M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
I

Infobip MCP Servers

Official
Infobip MCP Servers for omnichannel communication and messaging.
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #38 of 438
Stars
★ 37 Popular
Transport
Streamable HTTP · SSE
Runtime
Hosted (no local runtime)
Credentials
API key / credential required
License
MIT
Last commit
Tools
13
66FMRS · C

Infobip MCP Servers provide comprehensive remote messaging functionality, ideal for AI applications needing quick multi-channel integration. Officially maintained with thorough documentation, but watch for API key security and cost management.

Strongest · Setup experience 15/20 Weakest · Reliability 10/20

Reliability
10/20
Security and permissions
13/20
Maintenance
13/20
Documentation
15/20
Setup experience
15/20
Why each score
Reliability 10/20
Static-only review; no committed tests or CI evidence provided, so tool-list consistency and runtime behavior cannot be verified. The manifest lists 17 remotes while README advertises endpoints (whatsapp-flow, email, voice, camara, message, provision, deep-research) absent from the manifest, indicating manifest/repo drift. Not scored lower because error/troubleshooting guidance exists and endpoint structure is consistent.
Security and permissions 13/20
API keys correctly flagged as secrets with variable placeholders, dual OAuth 2.1 / API-key paths, no hardcoded credentials or red-line findings. However, streamable-http remotes declare headers isRequired:false while the variable is required, an internal contradiction that could allow unauthenticated connections; high-impact operations (sending messages, purchasing numbers) lack disclosed confirmation mechanisms, and the access-control section only defers to generic MCP guidelines.
Maintenance 13/20
MIT license, not archived, official vendor ownership, version 2.0.0, 32 stars, 17 open issues. Static material shows no release history, security-response channel, or dependency-update evidence, capping the score.
Documentation 15/20
Well-layered README: endpoint tables, transport guidance, OAuth 2.1 with scope discovery, API key format, feature/token-consumption matrix, early-access labeling, and troubleshooting. Deductions for missing tool-level parameter docs, only qualitative cost/limit information, and reliance on external docs for details.
Setup experience 15/20
Direct client config examples (JSON config, Authorization header format, OAuth auto-discovery), documented SSE fallback via /sse suffix, and fully remote hosting requiring no local runtime keep setup simple; capped at 15 absent verifiable execution evidence, plus multi-endpoint selection and manual scope configuration add friction on some clients.

Static review · not runListed 2026-09-08

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account data

Best for

  • Developers building AI agents that need diverse communication channels.
  • Enterprise solutions requiring rapid deployment and configuration.
  • Multi-tenant systems wanting to simplify API integrations.

Not for

  • Users needing only a simple single-channel solution with minimal resource usage.
  • Scenarios requiring fully on-premises or offline deployment.
  • Developers wanting manual fine-grained control of every message detail.

Required permissions

  • Requires an Infobip account and valid API key.
  • API key needs appropriate permissions per channel (e.g., SMS, WhatsApp) and scope.
  • For OAuth authentication, correct scopes must be configured.

Risks and side effects

  • Exposure of API keys can lead to unauthorized sending and charges.
  • Failed message sends may incur additional costs.
  • Reliance on external APIs and infrastructure can be affected by network and availability.
  • Misconfigured permissions may lead to unexpected high costs or privacy issues.

Setup

Before you start

Runtime：Hosted (no local runtime)

INFOBIP_API_KEY requiredsecret Your Infobip API key, obtained from your Infobip account; passed as the Authorization header 'App {INFOBIP_API_KEY}' on remote endpoints.
  1. Sign up for an Infobip account and obtain an API key.
  2. Connect a MCP-capable client to a remote endpoint, e.g., https://mcp.infobip.com/sms.
  3. Authenticate via OAuth 2.1 automatically, or set the 'Authorization' header manually: App ${INFOBIP_API_KEY}.

Check that it works

Connect your MCP client to https://mcp.infobip.com/sms with the Authorization header 'App ${INFOBIP_API_KEY}'; the send_sms and message-log tools should appear in your client's tool list, and calling account_balance (account-management server) should return your balance, proving authentication works.

Troubleshooting

  1. Authentication issues: Check API key validity and scope configuration.
  2. Message delivery failures: Ensure recipient phone number is correct and reachable.
  3. Connectivity issues: Check network restrictions and proxy settings.
  4. Refer to Infobip documentation for error codes and troubleshooting guides.

Things to try

Once connected, you can ask your AI assistant things like:

  • Send an SMS via Infobip to +385911234567 saying 'Your order has shipped'.
  • Check my Infobip account balance.
  • Search the Infobip docs for how WhatsApp template messages work.
  • Send a PIN to my phone over SMS and then verify the code I received.

Tools 13

send_sms destructive
Send and preview SMS messages with scheduling, bulk sending, multilingual support, and delivery reports.
send_whatsapp destructive
Send WhatsApp templates, text, media, location, and contact messages; manage templates and retrieve delivery reports.
send_viber destructive
Send Viber rich media messages with scheduling, delivery reports, and SMS failover.
send_rcs destructive
Send RCS rich messages (multimedia, suggested replies, carousels, barcodes) with capability check and SMS/MMS failover.
send_email destructive
Send email and bulk emails, with email address validation.
send_voice destructive
Initiate voice calls with text-to-speech or pre-recorded audio, manage conferencing, and get call reports.
send_push destructive
Send mobile push notifications, manage push applications and inbox messages.
send_pin writes
Send 2FA PIN codes via SMS, voice, or email and manage verification flows.
Show 5 more tools
verify_pin writes
Verify a user-provided PIN to complete 2FA verification.
search_docs read-only
Search Infobip documentation for API reference, use cases, and product guides.
manage_person writes
Manage customer profiles, company info, tags, attributes, and events.
account_balance read-only
Retrieve account balance and manage account details.
manage_application writes
Create and manage CPaaSX multi-tenant applications and entities.

Use cases

Integrate omnichannel messaging (SMS, WhatsApp, Viber, etc.) into AI agents.
Implement secure 2FA flows for user verification.
Manage customer data, platform accounts, and documentation search.

Supported clients

Claude Desktop
Generic MCP Client

Listed from the project's documentation, not tested by this site.

Overview

Infobip MCP Servers are the official MCP server collection from Infobip, allowing AI agents to interact with the Infobip platform via the Model Context Protocol. They support sending messages over channels like SMS, WhatsApp, Viber, RCS, Email, Voice, and Mobile Push, as well as 2FA verification, customer data management (People), account management, and documentation search. All servers are remotely hosted, support streamable HTTP and SSE transports, and can be authenticated via OAuth 2.1 or API key.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 63.3k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision c3498cbab3fa Data synced 2026-10-19 Read the FMRS scoring method