Infobip

Name: Infobip
Author: infobip

@infobip

About Infobip

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, RCS, WhatsApp, or Viber, or managing customer

#infobip #sms #rcs #whatsapp #viber #2fa #tfa #message #communication #cpass #people

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "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>"
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Infobip?

Infobip MCP Servers allow AI agents to interact with the Infobip platform through the Model Context Protocol (MCP). They enable actions such as sending messages over SMS, WhatsApp, Viber, or RCS, and managing customer data in a controlled environment. This server is for developers building AI agents that need to integrate with Infobip communication and customer management services.

How to use Infobip?

Configure your MCP client to connect to one of the available remote endpoints (e.g., https://mcp.infobip.com/sms for SMS). Authenticate using an Infobip API key via the Authorization: App ${INFOBIP_API_KEY} header, or use OAuth 2.1 if your client supports it. For agents that do not support remote MCP servers, use a bridge like mcp-remote (example configuration for Claude Desktop is provided in the README). The servers support streamable HTTP transport by default; append /sse to an endpoint URL for SSE transport.

Key features of Infobip

Send messages via SMS, WhatsApp, Viber, and RCS
Set up and run 2FA (two-factor authentication) flows
Store and activate customer information
Manage Infobip user accounts
Nine dedicated remote MCP servers for different functions
Supports both API key and OAuth 2.1 authentication

Use cases of Infobip

Automating customer communications across multiple messaging channels
Implementing two-factor authentication for user verification
Managing and activating customer contact data from AI agents
Administering Infobip user accounts programmatically

FAQ from Infobip

What authentication methods does Infobip support?

Infobip supports two authentication methods: an API key provided in the Authorization header as App ${INFOBIP_API_KEY}, and OAuth 2.1 (requires client support for dynamic metadata discovery).

Do I need an Infobip account to use this server?

Yes, you must have an Infobip account. You can create one with a free trial via the link provided in the README.

What transport protocols are available?

The servers use streamable HTTP transport by default. For SSE transport, append /sse to the endpoint URL (e.g., https://mcp.infobip.com/sms/sse). Note that OAuth flows are not triggered when using SSE endpoints.

Can I use this server with Claude Desktop?

Yes. Use a bridge like mcp-remote with a configuration that includes the endpoint URL, the Authorization header, and your API key. Example configuration is shown in the README.

What should I do if messages are not being delivered?

Ensure the recipient phone number is valid and reachable. For authentication or other issues, refer to the Infobip troubleshooting guide linked in the README.