Platfone - Receive SMS & Virtual Numbers MCP
platfone-comLABSCO SUMMARY
One endpoint per channel rather than one endpoint for everything, so an agent only gets the capability you connected it to.
The split is the design decision worth noticing: connect the SMS endpoint and that is all the agent can do, which is a real control when the tools in question spend money and reach customers. Coverage goes past sending into the operational parts — templates, sender registration, delivery reports, logs and account balance — so the follow-up questions after a send are answerable in the same conversation.
What it is
Infobip's own hosted servers, split by product: each messaging channel has its own endpoint, alongside 2FA, customer data, account management, multi-tenant provisioning and documentation search.
What you get
- SMS with previews, scheduling and rescheduling, bulk sending, transliteration and character-set handling, delivery reports, message logs and URL tracking
- WhatsApp across template messages, text and media, location and contact messages, template management, delivery reports and SMS failover, plus a separate endpoint for building and sending interactive Flows
- Viber and RCS with rich media, carousels, suggested replies and barcodes, capability checks, scheduling and failover to SMS or MMS
- Email sent singly or in bulk, scheduled messages managed, and addresses validated
- Voice calls to one or many recipients with text-to-speech or pre-recorded audio, conference calls, call management and call logs
- Mobile push notifications with delivery reports, push statistics, application management and inbox messages
- A cross-channel endpoint that sends text, image or file messages over SMS, RCS, MMS and Viber in a single call
- Two-factor authentication flows set up and run
- Customer data through the People endpoint: person and company profiles, tags, custom attributes and lists, event tracking and export, and audience segmentation
- Account management — balance, free message count, account details and audit logs — and CPaaS X applications and entities for multi-tenant messaging
- Infobip's own documentation searchable, with a deep-research endpoint for models that need to read the API reference at length
Requirements
An Infobip account, with a free trial available. Everything is remote at https://mcp.infobip.com over streamable HTTP, with SSE available by appending /sse to the endpoint — nothing to install. Authenticate with OAuth 2.1, which most clients trigger on first connection, or send an Infobip API key in the Authorization header as App followed by the key. The key's scopes decide what works; clients that cannot discover the supported scopes need them configured by hand, and they are published at the endpoint's authorization-server metadata.
Setup effort
Get your endpoint, then paste it — add your endpoint to your client with your key
USE CASES
01
Sending a message without writing an integration
Connect the channel's endpoint and send, with the delivery report available afterwards.
02
Getting a WhatsApp campaign out
Manage the templates, send the template messages, and fall back to SMS where WhatsApp does not land.
03
Finding out what happened to a send
Read the delivery reports and message logs for the channel in question.
04
Verifying a user
Set up the 2FA flow and run it from the same place as the rest of your messaging.
05
Working with your customer data
Manage person and company profiles, attributes and lists, and segment an audience before sending to it.
06
Checking the account before a large run
Read the balance and free message count, and the audit log of what has been done.
BEFORE YOU INSTALL
What to know first
Requires
- A client that can reach a remote MCP server over HTTP
- INFOBIP_API_KEY in your environment
Where it runs
The documented client connects to a hosted endpoint.
INSTALLATION
Connect your client
Add your endpoint to your client with your key.
Server setup
ENDPOINT URL
https://mcp.infobip.com/<YOUR_SERVER>Requirements
- Your Infobip API key in the Authorization header, written App <YOUR_API_KEY> — the Any MCP client configuration shows where it goes.
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"infobip-sms": {
"type": "http",
"url": "https://mcp.infobip.com/sms",
"headers": {
"Authorization": "App ${INFOBIP_API_KEY}"
}
}
}
}<YOUR_SERVER> in the endpoint is the product you connect: sms (as here), whatsapp, whatsapp-flow, viber, rcs, email, voice, mobile-app-messaging, message, provision, 2fa, camara, people, account-management, application-entity, search or deep-research. Each is a separate server — add one entry per product. Append /sse for SSE transport.
Values written as ${…} are filled in only by clients that expand variables.
