Infobip MCP

What Infobip/mcp MCP server does

Infobip/mcp MCP server connects MCP-compatible AI agents and applications to Infobip services through hosted remote endpoints. Rather than exposing one general-purpose interface, the project provides separate servers for messaging channels, authentication and verification, customer data, account administration, CPaaS X resource management, and developer documentation.

Messaging endpoints cover SMS, WhatsApp, WhatsApp Flows, Viber, RCS, Email, Voice, and mobile app messaging. Depending on the channel, agents can send messages, schedule or manage them, retrieve delivery reports and logs, configure templates, or use channel-specific features such as rich media, failover, tracking, and interactive content. An early-access Message endpoint can send text, image, or file URL messages across several channels in one tool call.

Other endpoints support 2FA flows, telco-related verification capabilities, customer and company profiles, tags, custom attributes, lists, events, audience segmentation, account details, audit logs, and CPaaS X applications and entities. Documentation and Deep Research endpoints let agents search Infobip API references, product guides, use cases, and detailed documentation content.

How it works

Infobip/mcp MCP server uses streamable HTTP transport. Each capability group has its own URL under https://mcp.infobip.com, such as /sms, /whatsapp, /2fa, /people, or /search. An MCP client connects directly to the endpoint it needs using an HTTP server configuration:

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

Clients that require Server-Sent Events can append /sse to an endpoint. For example, the SMS endpoint becomes https://mcp.infobip.com/sms/sse.

Setup and configuration

Using Infobip/mcp MCP server requires an Infobip account and an MCP-compatible AI agent or application. Infobip offers a free trial for account creation. Authentication can use OAuth 2.1 when the MCP client supports OAuth 2.1 and authorization-server discovery; the authorization flow can then start automatically on the first connection. The README also documents API-key authentication as an alternative.

Configuration is endpoint-specific. Add only the Infobip service areas required by the agent, such as SMS for text messaging or People for customer profile operations. The material does not specify local package installation commands or environment variable names; the documented connection method is to use the hosted HTTP endpoints.

Tools and capabilities

• Send and schedule messages through multiple Infobip channels.
• Manage WhatsApp templates and interactive WhatsApp Flows.
• Run 2FA PIN delivery, resend, verification, and status operations.
• Manage people, companies, attributes, tags, lists, and events.
• Configure senders and purchase numbers through the early-access Provisioning endpoint.
• Search Infobip documentation or retrieve content for research workflows.

Limitations and notes

The available operations vary by endpoint and channel. Provisioning and Message are marked early access in the provided material. Some features, such as OAuth 2.1, depend on capabilities implemented by the MCP client. An Infobip account is required, and the documentation does not establish that all listed capabilities are available under a free account.