Infobip MCP server
Infobip in any MCP client, through Memtro: Infobip does not publish this server. Memtro's Infobip connector reads Infobip through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Infobip messaging: delivery logs of SMS and email sent in the last 48 hours (sender, recipient, status, error and when, filterable by recipient, sender or bulk), email sending domains with their DNS checks, and the status of a scheduled bulk. Can send an SMS or an email, pause, resume or cancel a scheduled bulk, and create or update a person in People, each only when asked.
Reads
infobip_sms_logsInfobip SMS sent in the last 48 hours (older logs do not exist): message and bulk id, sender, recipient number, when sent and finished, parts…infobip_email_logsInfobip emails sent in the last 48 hours (older logs do not exist): message and bulk id, sender, recipient address, when sent and finished…infobip_email_domainsInfobip email sending domains: id, name, whether active or blocked, open, click and unsubscribe tracking…infobip_scheduled_bulkThe status of a scheduled Infobip SMS or email bulk by its bulk id: PENDING, PAUSED, PROCESSING, CANCELED, FINISHED or FAILED.
Acts, when you ask
These change something in Infobip. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
infobip_send_smsSend an SMS through Infobip to up to 10 numbers, now or scheduled.infobip_send_emailSend an email through Infobip from a verified sending domain, now or scheduled.infobip_set_bulk_statusPause, resume or cancel a scheduled Infobip SMS or email bulk by its bulk id.infobip_create_personCreate a person in Infobip People with a name, an email and/or a phone, an external id and tags.infobip_update_personUpdate a person in Infobip People by id: first and last name are replaced if given; tags, emails and phones given are added to those already there…
Connect it
First connect Infobip on Dashboard → Connections, then add Memtro to your client once. The Infobip tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Infobip connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which SMS failed to deliver today?
- › Was the email to dan@bigco.example delivered?
- › Is the DNS for our sending domain verified?
- › What is the status of tomorrow's scheduled bulk?
- › Pause the scheduled bulk for the spring promotion
Questions
- Is this an official Infobip MCP server?
- No. It is Memtro's MCP server with Memtro's Infobip connector behind it: the connector reads Infobip through its API with the credentials you connect on Dashboard → Connections, and Infobip publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Infobip?
- Only when you ask, and only what it has been granted: send an SMS (billed per message part, reaches real people); send an email (billed, reaches real people); pause, resume or cancel a scheduled SMS or email bulk; create a person in People; update a person in People (names replaced, tags and contacts added). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.