Infobip MCP Servers

Infobip's official remote MCP servers: SMS, WhatsApp, Viber, RCS, email, voice, push, 2FA and customer data

MCP serverHigh risk

infobip/mcp

Install

{
  "mcpServers": {
    "infobip-sms": {
      "type": "http",
      "url": "https://mcp.infobip.com/sms"
    }
  }
}

With OAuth 2.1 support, auth starts on first connection. For other areas change the path: /whatsapp, /email, /2fa and so on.

This is third-party code. Review the repository files before installing.

What it does

Infobip hosts a set of separate MCP servers, one per area, and the agent connects to the ones it needs over HTTP. Channel servers send messages, including scheduled and bulk sends, manage WhatsApp templates and fetch delivery reports. The Provisioning server helps register a sender or buy a number. The 2FA and CAMARA servers send and verify PINs and check numbers or SIM swaps. There are also servers for customer profiles, account management and Infobip documentation search.

Who it is for. For developers and support teams building messaging and communications on Infobip.

Good fit when

  • You want the agent to send customer notifications via SMS or WhatsApp
  • You need to set up PIN-based two-factor auth quickly
  • You need help with the Infobip API through documentation search

Not a fit when

  • You have no Infobip account
  • The agent must not message real recipients without review

Example request

Send an SMS to the test number saying your order has shipped and show the delivery report

Limitations

Requires an Infobip account, and sending messages costs money. Auth is OAuth 2.1 if your client supports it, otherwise an API key in the Authorization header. Servers with many tools, such as RCS and WhatsApp, consume many tokens; for simple notifications the README suggests the Message server. Message and Provisioning are in early access. Service availability from Russia without a VPN is unverified.

How to disable. Remove the Infobip server blocks from your MCP config and revoke the API key in your Infobip account.

MCP

Transport
http, sse
Authentication
OAuth
Environment variables
Environment variables
INFOBIP_API_KEY
secret
Infobip API key if the client does not support OAuth 2.1.

Security check

  • Sends paid messages to real recipients
  • Buys numbers and changes customer and account data

README in short

The README lists remote servers with URLs and features, explains HTTP connection and two auth methods: OAuth 2.1 and an API key. It has a comparison table of messaging servers by features, tool count and token usage, plus sections on limiting agent permissions and troubleshooting. The examples folder covers OpenAI Agents SDK, LangGraph and Semantic Kernel. MIT licensed.

FAQ

Do I need to connect every server?

No, each server covers one area. Connect only what you need to avoid spending tokens on extra tools.

Is SSE supported?

Yes, append /sse to the server URL, for example https://mcp.infobip.com/sms/sse.

Editors’ pick

An MCP server with n8n node and template knowledge: the agent picks nodes, validates configs and, with API access, creates workflows in your n8n

MCP serverHigh risk22.9K
Editors’ pick

Zapier's official MCP plugin: the agent gets actions across thousands of apps through your Zapier account

PluginHigh risk409

A curated list of Claude skills and plugins, plus Composio's own automation skills for 78 SaaS apps

SkillHigh risk75K

A plugin and CLI catalog for agents: generates command-line interfaces for GUI apps like GIMP and Blender and installs ready ones via CLI-Hub

PluginHigh risk49.4K