Cursor plugin for Infobip's remote MCP (Model Context Protocol) servers. Connect Cursor's AI agent directly to Infobip's messaging platform to send messages, manage verification flows, and query account data across channels, no custom integration code required.
Built from the specs published in infobip/mcp. See infobip.com/docs/mcp for full product documentation.
| Server | Endpoint | Description |
|---|---|---|
| SMS | /sms |
Send/preview messages, scheduling, bulk sending, multilingual support, delivery reports, message logs, URL tracking |
/whatsapp |
Template messages, text/media sending, template management, delivery reports, SMS failover | |
| WhatsApp Flow (Early Access) | /whatsapp-flow |
Create/manage static & dynamic flows, interactive components, flow JSON management |
| Viber | /viber |
Rich media messaging (images, videos, files), scheduling, SMS failover, URL tracking |
| RCS | /rcs |
Rich messages with multimedia, suggested replies, carousels, barcodes, SMS/MMS failover |
/email |
Send email messages, bulk sending, scheduling, email address validation | |
| Voice | /voice |
Single/multi-recipient calls, text-to-speech, pre-recorded audio, conference calls, call logs |
| Message (Early Access) | /message |
Multi-channel (SMS, RCS, MMS, Viber) sending in a single tool call |
| 2FA | /2fa |
Application management, PIN templates (SMS/Email/Voice), verification workflows |
| Account Management | /account-management |
Account balance, free messages count, account details, audit logs |
| Infobip Documentation | /search |
Documentation search, API reference, use cases, product guides |
| Infobip Deep Research | /deep-research |
Deep search across API documentation, detailed content retrieval |
Base URL: https://mcp.infobip.com
- A valid Infobip account (a free trial is available)
- Cursor with MCP support enabled
This plugin's mcp.json uses OAuth 2.1 by default, so no secrets are stored in the config. Cursor triggers the authorization flow automatically on first connection to each server.
If your setup requires an API key instead, add an Authorization header to the relevant server entry in mcp.json:
{
"type": "http",
"url": "https://mcp.infobip.com/sms",
"headers": {
"Authorization": "App ${INFOBIP_API_KEY}"
}
}Set INFOBIP_API_KEY in your environment. See API authentication for details on generating a key.
- Infobip MCP documentation
- infobip/mcp on GitHub (source of truth for server specs)
- Provisioning MCP docs
MIT, see LICENSE.