home / mcp / infobip mcp server
Infobip Remote MCP Servers Documentation
Configuration
View docs{
"mcpServers": {
"infobip-mcp": {
"url": "https://mcp.infobip.com/sms"
}
}
}Infobip MCP Servers enable you to build AI agents that interact with the Infobip platform using the Model Context Protocol (MCP). You can connect your agents to Infobip to perform actions such as sending messages across channels like SMS, WhatsApp, or Viber, and managing customer data in a production-ready environment.
Connect your MCP client to Infobip MCP servers using either an HTTP transport to a remote MCP server or a STDIO bridge for local or containerized setups. Once connected, you can instruct your AI agents to send messages, manage flows, verify numbers, access account information, and perform various channel-specific actions through the MCP endpoints.
Prerequisites: ensure you have a modern runtime environment available for your MCP client (Node.js for JavaScript/TypeScript or Python, depending on your client). You will also need an Infobip account with a valid API key for authentication.
Step 1: Create a configuration that points to the Infobip MCP server you want to use. You can choose either an HTTP (remote) transport or a STDIO (local) transport.
Step 2: Provide your authentication details. For HTTP transport, include your API key in the Authorization header as shown in the examples. For STDIO transport, pass the API key through an environment variable and reference it in the command arguments.
Step 3: Run your MCP client with the selected transport configuration. The following examples show the exact configurations you can copy into your project.
{
"mcpServers": {
"ib-sms": {
"type": "http",
"url": "https://mcp.infobip.com/sms",
"headers": {
"Authorization": "App ${INFOBIP_API_KEY}"
}
}
}
}{
"mcpServers": {
"infobip-sms": {
"type": "stdio",
"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>"
}
}
}
}If your client supports dynamic metadata discovery, you can enable OAuth 2.1 authentication with automatic redirects to the Infobip OAuth server. Ensure your client can discover or be configured with the correct scopes for the chosen MCP server, which are listed in the OAuth server metadata.
You can authenticate using an API key in the Authorization header or use OAuth 2.1 flow if your MCP client supports it. When using OAuth 2.1, your client should initiate the flow by connecting to the MCP server without credentials and let the OAuth server handle authentication.