MCP servers

Infobip hosts remote Model Context Protocol (MCP) servers that expose Infobip API operations as tools for AI agents. Connect any MCP client that supports remote servers, such as Claude Code, Cursor, VS Code, Codex CLI, or an agent framework. The agent can then act on your account. For example, it can set up senders and numbers, send messages, verify users, manage contacts, monitor traffic and costs, and search the Infobip docs. For an overview of the servers and what agents can do with them, see Infobip MCP servers.

Connect an MCP client

To connect, configure the following:

• URL: https://mcp.infobip.com/{server}. Each product has its own server, for example /sms, /whatsapp, or /provision.
• Transport: Streamable HTTP. For legacy SSE clients, append /sse (/sms/sse). For clients without remote MCP support, use the mcp-remote(opens in new tab) STDIO bridge.
• Authentication: OAuth 2.1 or an API key with the scopes the server needs.
  • OAuth 2.1: If your client supports OAuth 2.1, leave out the Authorization header. The client opens the Infobip sign-in on first connection. For details, see OAuth 2.1.
  • API key: Send Authorization: App {API_KEY}.

The configuration format and environment variable syntax differ by client. Check the MCP docs of your client.

Choose servers

The GitHub README(opens in new tab) is the current list of servers, endpoints, and tools. Each connected server loads its tool definitions into the context of the agent, so connect only the servers the task needs.

The following servers are available in Early Access:

• Provision MCP: The agent registers senders, buys numbers, and configures channel senders, so the setup before the first message happens in the same conversation.
• Message MCP(opens in new tab): The agent sends text, image, or file messages across SMS, RCS, MMS, and Viber in one step.
• Observe MCP: The agent reads traffic metrics, billing usage, error codes, and message logs to explain what happened to traffic you already sent.

Before an agent acts on your account

Keep the following in mind:

• Tool calls are real API calls. Messages are sent and billed.
• If your client supports it, keep approval on for tools that send messages.
• Give API keys only the scopes the server needs, for example sms:message:send. With OAuth, the client requests the scopes itself. If it does not discover them, set them manually from {server-url}/.well-known/oauth-authorization-server.
• On a self-signup account on the free trial, messages can only go to verified numbers.
• Keep API keys out of MCP config files that are committed to version control.