Infobip Message

Send real SMS, RCS, MMS and Viber messages from an AI agent via Infobip.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Infobip Message connector does

The Infobip Message MCP server lets Claude and other AI agents send text, image or file-link messages over SMS, RCS, MMS and Viber through one tool, then check delivery status. Messages reach real phone numbers and draw on your Infobip account. Sign-in is OAuth; Infobip labels the server early access.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Infobip Message tools (2)

  • check_status
  • send

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Early access. Infobip's README badges the Message server early access, and its main "Using MCP servers" endpoint table did not list it on 2026-11-18. Expect changes.
  • No scheduling, bulk sends or message logs. Infobip's matrix lists none of these for the Message server; use the per-channel servers for them.
  • Delivery reports may not be live yet. Infobip's matrix says "planned" while the directory lists check_status.
  • Trial accounts send only to verified numbers.
  • No WhatsApp, email or voice. Those channels have their own Infobip servers.
  • We could not read tool schemas. The endpoint requires OAuth, so parameters and annotations are not shown here; tool names come from Anthropic's directory.
  • Channel rules still apply. Sender registration and market rules for SMS, RCS and Viber are set in your Infobip account, not by the connector.

Frequently asked questions

Can I test the Infobip Message connector on a free trial?

Yes, with one restriction. Infobip states that a free trial account includes messaging units for testing its MCP servers, but during the trial messages can only be sent to verified numbers. A send to any other number will not be delivered, so verify the test recipient's number in your Infobip account first. Infobip lists the same restriction under message delivery troubleshooting.

Can I use an Infobip API key instead of OAuth?

Yes. Infobip documents two ways to authenticate: OAuth 2.1, which an MCP client such as Claude triggers automatically on first connection, or an Infobip API key sent in the Authorization header in the form App followed by the key. The API key must carry the right scope for the server you connect, and Infobip warns against hardcoding it or committing it to version control.

Why does the connector fail to authorise?

Usually a scope or client problem. Infobip's troubleshooting advice is to check that you have a valid account and an API key with the correct scope, that your MCP client supports OAuth metadata discovery, and that the required scopes are configured. Clients that cannot discover scopes automatically can read them from the server's oauth-authorization-server metadata document and set them by hand.

How is the Message server different from Infobip's SMS server?

It trades features for a smaller footprint. Infobip's comparison table shows the Message server covering SMS, RCS, MMS and Viber in one or two tools, with minimal token consumption. The dedicated SMS server has ten tools and adds scheduling, bulk sending, transliteration, message logs and URL tracking. Infobip recommends Message for simple notifications that need none of those.

Sources

Use it in an agent

Put Infobip Message to work.

Connect Infobip Message once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.