Infobip MCP Servers is a collection of official remote MCP servers provided by Infobip, designed to let AI agents interact with the Infobip platform through the Model Context Protocol (MCP) and perform operations in a controlled, production-grade environment. Its goal is to reduce complex integrations and documentation lookups, allowing agents to directly perform communication and account management tasks.
Main capabilities include:
- Message sending: Send messages through channels such as SMS, WhatsApp, RCS, Email, Viber, Voice, and Mobile push.
- Channel and number management: Register senders, purchase numbers, and manage channel settings.
- Data querying: Query delivery metrics, billing usage, error codes, and message logs.
- Authentication and verification: Set up and run 2FA flows; use telecom network capabilities to improve authentication methods and enhance online transaction security.
- Customer and account management: Store and activate customer information; manage Infobip user accounts; orchestrate multi-tenant workflows through CPaaS X.
- Developer resources: Explore Infobip documentation; enable deep research models to search and retrieve Infobip documentation as a data source.
Usage:
- Prerequisites: An Infobip account is required (a free trial is available), as well as an AI agent or application that supports an MCP client.
- Connection: The remote MCP server base URL is https://mcp.infobip.com，支持可流式 HTTP transport, which can connect MCP clients directly to any endpoint; for SSE transport, append /sse to the endpoint URL (for example, https://mcp.infobip.com/sms/sse）。不同框架的使用示例见仓库的 examples directory.
- Authentication and authorization: Supports OAuth 2.1. If the MCP client supports OAuth 2.1 and authorization server discovery, the first connection will automatically trigger the authorization flow and redirect to the Infobip OAuth server; if the client does not support automatic discovery of scopes_supported, the scopes must be manually configured in the client configuration. The specific scopes can be obtained from {server-url}/.well-known/oauth-authorization-server, for example, for the SMS server it is https://mcp.infobip.com/sms/.well-known/oauth-authorization-server。也可使用 API Key, provided in the Authorization header in the format App ${INFOBIP_API_KEY}.
- Permission governance: It is recommended to implement fine-grained permission control, especially for high-risk operations such as sending messages; unrestricted access permissions will bring security vulnerabilities and operational risks. Official MCP implementation guidelines should be followed.
- Server selection: Different MCP servers expose different numbers of tools, which directly affects the tokens consumed by each agent call. For simple notification scenarios that do not require scheduling, logging, or channel-specific management, the Message MCP server is the lowest-overhead option.
Applicable scenarios:
- Build AI agents that can send multi-channel messages, run 2FA, and manage customer data and accounts.
- Orchestrate multi-tenant workflows in CPaaS scenarios.
- Enable research-oriented models to retrieve Infobip documentation as a data source.
Limitations and notes:
- Requires an Infobip account and a supported MCP client.
- OAuth 2.1 usage depends on client support for dynamic metadata discovery; otherwise, scopes must be configured manually.
- Message delivery depends on a valid recipient phone number.
- The documentation does not provide specific fees, pricing, or performance data, and none is currently provided.
- The repository documentation uses the MIT License.
