Other · Remote MCP server
infobip.com
Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.infobip/mcp- Version
- 2.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, SSE (HTTP + Server-Sent Events)
- Published
- 2025-10-20
- Updated
- 2025-10-20
- Publisher
- com.infobip
- Namespace
- Namespace verified by the MCP Registry via the domain infobip.com · how
- Listed under
- WhatsApp MCP servers
- Repository
- github.com/infobip/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.infobip.com/sms | Authorization (secret) |
| SSE (HTTP + Server-Sent Events) | https://mcp.infobip.com/sms/sse | Authorization (required, secret) |
| Streamable HTTP | https://mcp.infobip.com/whatsapp | Authorization (secret) |
| SSE (HTTP + Server-Sent Events) | https://mcp.infobip.com/whatsapp/sse | Authorization (required, secret) |
| Streamable HTTP | https://mcp.infobip.com/viber | Authorization (secret) |
| SSE (HTTP + Server-Sent Events) | https://mcp.infobip.com/viber/sse | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://mcp.infobip.com/sms(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
- Endpoint
https://mcp.infobip.com/sms/sse(SSE)- Reachable
- Yes (HTTP 401)
- SSE stream
- Not opened: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
- Endpoint
https://mcp.infobip.com/whatsapp(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
- Endpoint
https://mcp.infobip.com/whatsapp/sse(SSE)- Reachable
- Yes (HTTP 401)
- SSE stream
- Not opened: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
- Endpoint
https://mcp.infobip.com/viber(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
- Endpoint
https://mcp.infobip.com/viber/sse(SSE)- Reachable
- Yes (HTTP 401)
- SSE stream
- Not opened: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect infobip.com
infobip.com is a remote MCP server: there is nothing to install. Its endpoints are https://mcp.infobip.com/sms, https://mcp.infobip.com/whatsapp and https://mcp.infobip.com/viber, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
It also lists endpoints on the older SSE transport https://mcp.infobip.com/sms/sse, https://mcp.infobip.com/whatsapp/sse and https://mcp.infobip.com/viber/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Inflation SignalInflation & Fed liquidity thermometer: 47 macro series, too_low..too_high. Pay-per-call x402. | Remote · HTTPLive check: ✓ handshake |
| InflowMCP Server for agents to onboard, pay, and provision services autonomously with InFlow. | Remote · HTTPLive check: sign-in required |
| InfluencePlan social campaigns, draft and review posts, schedule approved publishing, and read Insights. | Remote · HTTPLive check: sign-in required |
| InfluSense AIRead-only access to InfluSense influencer discovery, ratings, watchlists, and reports via MCP. | Remote · HTTPLive check: sign-in required |
| InfoLang MemoryInfoLang semantic memory MCP - investigate, memorize, and recall compressed agent context. | Remote · HTTPLive check: ✗ no handshake |
| InforcerRead-only MCP server for Inforcer M365 baseline governance, plus assessment and report runs. | Local · stdio |
| InforcerRead-only MCP server for Inforcer M365 baseline governance, plus assessment and report runs. | Local · stdio |
| InfoTrack (US)Court e-filing and process serving. Submit filings, serve process, and manage orders. | Remote · HTTPLive check: sign-in required |