Infobip MCP Servers let you build AI agents to interact with the Infobip platform through the Model Context Protocol (MCP). Connect to Infobip and enable your agents to perform actions, such as sending messages over channels like SMS, WhatsApp, or Viber, or managing customer data in a controlled, production-grade environment.
No more complex integrations or digging through endless documentation. Just plug in and let your AI do the talking.
- ✉️ Send messages using channels like SMS, WhatsApp, Viber, or RCS (more coming soon)
- 📱 Set up and run 2FA flows
- 🧑💼 Store & activate your customer information
- 👤 Manage Infobip user accounts
Infobip remote MCP servers support streamable HTTP transport. Below is a list of available remote MCP servers.
Base URL: https://mcp.infobip.com
Server | Endpoint |
---|---|
SMS | https://mcp.infobip.com/sms |
https://mcp.infobip.com/whatsapp |
|
Viber | https://mcp.infobip.com/viber |
RCS | https://mcp.infobip.com/rcs |
Messages API | https://mcp.infobip.com/messages-api |
2FA | https://mcp.infobip.com/2fa |
People | https://mcp.infobip.com/people |
Account Management | https://mcp.infobip.com/account-management |
For more details on supported endpoints, see the Infobip MCP documentation.
If your agent does not support remote MCP servers, you can use a bridge like mcp-remote.
Example configuration for Claude Desktop:
{
"mcpServers": {
"infobip-sms": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.infobip.com/sms",
"--header",
"Authorization: App ${INFOBIP_API_KEY}"
],
"env": {
"INFOBIP_API_KEY": "<Your Infobip API Key here>"
}
}
}
}
To use Infobip MCP servers, you need an Infobip account. If you don't have one, create an Infobip account with a free trial.
If your MCP client supports adding additional headers through configuration or environment variables, you can use your Infobip API key and provide it in the Authorization
header using the following format: App ${INFOBIP_API_KEY}
.
See the mcp-remote
example above for setup details.
Infobip MCP servers support OAuth 2.1 authentication. To use OAuth 2.1, your MCP client must support OAuth 2.1 authentication and dynamic OAuth authorization server metadata discovery. To start the OAuth flow, configure your MCP client to connect to the Infobip MCP server without providing authentication credentials. Your MCP client should initiate the OAuth flow automatically, redirecting you to the Infobip OAuth server for authentication.
Some MCP clients may not support automatic scopes_supported
discovery.
In this case, you must manually configure the scopes in your MCP client configuration.
The scopes for a particular MCP server can be found in the authorization server metadata at {server-url}/.well-known/oauth-authorization-server
.
For example, for the Infobip SMS MCP server, the scopes are available at: https://mcp.infobip.com/sms/.well-known/oauth-authorization-server
Example configuration for Claude Desktop:
{
"mcpServers": {
"infobip-sms": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.infobip.com/sms",
"--debug",
"--static-oauth-client-metadata",
"{\"scope\":\"sms:manage profile\"}"
]
}
}
}
Authentication and Authorization Issues
- Ensure you have a valid Infobip account and an API key with a correct scope.
- If using OAuth 2.1, verify your MCP client supports dynamic metadata discovery.
- Confirm that required scopes are correctly configured in your MCP client.
Message Delivery Issues
- Make sure the recipient phone number is valid and reachable.
Other Issues
- For HTTP status codes and error details, see the troubleshooting guide.
If you have suggestions for improvements, please contact devrel@infobip.com.
This document is licensed under the MIT License. See LICENSE for details.
Happy building with Infobip MCP! 🚀