Servers¶
RingCentral currently publishes four active MCP servers. All implement the Model Context Protocol specification and are reachable over HTTPS using Server-Sent Events (SSE) transport.
Call logs, AI call notes, SMS, fax, and voicemail from the message store.
View server →Team messaging (Glip): chats, direct conversations, teams, and posts.
View server →Tool discovery, generic API dispatch, extension, presence, and directory search.
View server →Bridges RingCentral telephony with your connected CRM — contacts, call logging, and more.
View server →Server registry¶
| Server | URL | Status | Tools |
|---|---|---|---|
| RingEx Phone | https://mcp.labs.ringcentral.com/ringex/phone |
🟡 Labs / Beta · New | 24 |
| RingEx Chat | https://mcp.labs.ringcentral.com/ringex/team-chat |
🟡 Labs / Beta · New | 65 |
| RingEx Admin | https://mcp.labs.ringcentral.com/ringex/admin |
🟡 Labs / Beta · New | 26 |
| App Connect | https://unified-crm-extension.labs.ringcentral.com/mcp |
🟢 Available | 9 |
Transport & protocol¶
Both servers use SSE (Server-Sent Events) transport over HTTPS, which is the recommended transport for remote MCP servers. Clients connect by sending an HTTP POST to the server URL with a JSON-RPC 2.0 body.
# Discover tools on any server
curl -X POST https://<server-url> \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
Authentication model¶
- RingEx Phone / Chat / Admin — no authentication required for tool discovery; most tools require a valid RingCentral session.
- App Connect — tools marked ⚠️ REQUIRES CRM CONNECTION require the user to have authenticated with both RingCentral and a supported CRM platform.
Versioning policy¶
Labs servers follow a rolling-release model. Breaking changes will be announced in the Changelog with at least 14 days notice. Stable tools are versioned via api-version query parameter where applicable.