Overview

Infobip MCP Server lets AI agents interact with Infobip’s communications platform using the Model Context Protocol (MCP). Instead of implementing numerous vendor APIs, agents connect to a remote MCP endpoint and perform messaging and customer-management actions (SMS, WhatsApp, Viber, RCS, Voice, push notifications, 2FA flows, and more) through a consistent, production-ready protocol and transport.

This approach simplifies integration for generative agents and tools that understand MCP: the agent issues high-level requests to an MCP server, and the server handles channel specifics, rate limiting, delivery reports, and platform security. It supports streamable HTTP transports (including a server-sent events variant) so agents can receive events (delivery reports, inbound messages, verification results) in real time.

Features

Send messages across multiple channels: SMS, WhatsApp, Viber, RCS, Voice, Mobile Push
Manage templates, flows and interactive components for WhatsApp and RCS
Two-factor authentication (PIN send/resend/verify) and telco verification features (SIM swap, device verification)
Customer and account management (Person profiles, tags, attributes, account balance, audit logs)
CPaaS X support for multi-tenant applications and resources
Documentation search and deep-research endpoints for agent-driven knowledge retrieval
Streamable HTTP transport with optional SSE path for event streaming (/sse)

Installation / Configuration

Create an Infobip account (trial available).
Choose authentication method: API Key or OAuth 2.1.
Configure your AI client to connect to one or more MCP endpoints.

Example mcpServers configuration (JSON) for a generic AI client:

{
  "mcpServers": {
    "ib-sms": {
      "url": "https://mcp.infobip.com/sms",
      "auth": {
        "type": "apiKey",
        "header": "Authorization",
        "prefix": "App ",
        "key": "YOUR_API_KEY"
      }
    },
    "ib-whatsapp": {
      "url": "https://mcp.infobip.com/whatsapp",
      "auth": {
        "type": "oauth2",
        "token_url": "https://auth.infobip.com/oauth2/token",
        "client_id": "YOUR_CLIENT_ID",
        "client_secret": "YOUR_CLIENT_SECRET"
      }
    }
  }
}

Opening an HTTP connection (streamable) with curl using an API key:

curl -N -H "Authorization: App YOUR_API_KEY" \
     -H "Content-Type: application/mcp-json" \
     https://mcp.infobip.com/sms

If you need server-sent events (SSE) for the same endpoint, append /sse:

curl -N -H "Authorization: App YOUR_API_KEY" \
     -H "Accept: text/event-stream" \
     https://mcp.infobip.com/sms/sse

Authentication notes:

API Key: include header “Authorization: App {API_KEY}” (or the header/prefix your client uses).
OAuth 2.1: obtain a bearer token from Infobip’s token endpoint and use “Authorization: Bearer {access_token}”.

Adjust headers/content-type to match your MCP client/library expectations.

Available Resources

Key remote MCP endpoints (base URL: https://mcp.infobip.com)

Category	Endpoint (path)	Purpose
Messaging	/sms, /whatsapp, /viber, /rcs, /voice, /mobile-app-messaging	Send messages, media, voice calls, push notifications
WhatsApp Flow	/whatsapp-flow	Build and send interactive flows and components
Authentication	/2fa, /camara	PIN flows, number/device verification, SIM swap checks
People & Accounts	/people, /account-management, /application-entity	Customer profiles, account info, CPaaSX resource management
Developer Tools	/search, /deep-research	Doc search and deep documentation retrieval for agents

For full details and per-endpoint capabilities consult Infobip MCP docs and the GitHub repository: https://github.com/infobip/mcp

Use Cases

Send transactional SMS from an agent: an e-commerce assistant confirms an order and instructs the MCP server to send an SMS confirmation. The agent emits an MCP “send message” action to /sms; the server returns a delivery report asynchronously via the stream.
WhatsApp templated notifications: a support bot triggers a pre-approved WhatsApp template to notify a customer. Templates, quick replies and interactive forms are managed through the /whatsapp and /whatsapp-flow endpoints.
2FA and verification: an authentication agent requests a PIN via /2fa (SMS or voice) and waits for verification result events streamed back to the agent connection.
Customer profile orchestration: a CRM assistant creates or updates Person profiles via /people, tags customers, and queries audiences for targeted campaigns.
Multi-tenant application management: platform tools orchestrate CPaaS X apps and resource allocation through /application-entity to support multiple customers under one platform.

Troubleshooting

If you need real-time events and don’t receive them, try the SSE path (append /sse) and ensure your client accepts text/event-stream.
Check authentication headers and token expiry for OAuth flows.
Use the documentation search (/search) to let agents discover correct endpoints and payload structures.

Infobip MCP Server for AI Agent Messaging