ringcentral-mcp
This server gives you read-only, MCP-based access to a RingCentral cloud phone (UCaaS) account's core data — account details, extensions, phone numbers, presence, call queues, contacts, and call logs/recordings — via 13 tools that proxy the RingCentral REST API using per-request JWT credentials.
Account info — get basic company/account details (
ringcentral_get_account_info).Extensions — list extensions with filters (type, status, extension number, email) or fetch a single extension's details.
Phone numbers — list company and extension numbers, filtered by usage type or status.
Presence — check whether an extension is available, on a call, or in do-not-disturb.
Call queues — list queues and enumerate the members staffing each queue.
Contacts — list the company directory (internal contacts) and an extension's personal address book (external contacts).
Call logs — pull company-wide or per-extension call history, filtered by date range, view (Simple/Detailed), direction, and call type.
Recordings — retrieve recording metadata (including a
contentUridownload link) and the media's content-type/size by recording ID taken from a call log entry.
Constraints worth noting: all tools are read-only; every /mcp request must carry X-RingCentral-Client-Id, X-RingCentral-Client-Secret, and X-RingCentral-Jwt headers; per_page is hard-capped at 200; the recording "download" tool returns metadata only, not audio bytes; and the server has not yet been validated against a live RingCentral account.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ringcentral-mcp what is the current presence of extension 102?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ringcentral-mcp
RingCentral MCP Service — a stateless HTTP MCP server wrapping the RingCentral REST API, covering account info, extensions, phone numbers, presence, call queues, contacts, and call logs/recordings.
Tech stack: Python 3.12 + uv + FastMCP (Starlette/Uvicorn)
MSPbots Connector
The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.
Get started at connect.mspbots.ai →
MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.
Hosted service: connect.mspbots.ai · Free to use.
Why Connector

Visible | Every tool call is logged: who, which vendor, when. Usage dashboard, CSV export, SIEM streaming. |
Controlled | Role-based, per-tool allowlist. Deny by default. |
Protected | Credentials encrypted per record. AI clients never see your vendor passwords or tokens. |
MSP-native | Built for the MSP stack only: RMM, PSA, documentation, security, finance. |
Quick start
Sign up at connect.mspbots.ai.
Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.
Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.
Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.
Ask your AI to do real work, and watch every call appear in the audit log.
Features
Unified gateway
One MCP URL for all your AI clients
150+ connectors across the MSP stack
Custom MCP servers supported, free
Authorization happens on each vendor's own page; the AI never sees passwords or tokens
Bring your own credentials: use the vendor API keys you already have
Multiple accounts per app; connect once, reuse across AI clients
Tool search: finds the right action for the task
One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically
Visibility
Audit log for every tool call (who, which vendor, when)
Usage dashboard: call volume, top vendors, error rate, per-user activity
Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)
Optional recording of tool arguments and result summaries (off by default, enabled per organization)
Control
Per-role, per-tool allowlist, deny by default
owner / admin / member roles
SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace
Security
Credentials encrypted one record at a time (AES-256-GCM, per-record key)
AI clients authenticate with OAuth 2.1 + PKCE
Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.
Static egress IP for customer firewall and API allowlisting
Pricing
Free.
Links: connect.mspbots.ai · mspbots.ai
Related MCP server: bvoip-mcp
What is RingCentral / when would an agent use this
RingCentral is a cloud phone / UCaaS (telephony) platform MSPs use to manage a customer's business phone system — extensions, phone numbers, presence, call queues, directory/personal contacts, and call history. An agent should reach for this MCP for requests like:
"Who has extension 101 / what extensions exist?" →
ringcentral_list_extensions,ringcentral_get_extension"Is this person available / on a call right now?" →
ringcentral_get_presence"Which numbers are provisioned for this account?" →
ringcentral_list_phone_numbers"Who staffs the support call queue?" →
ringcentral_list_queues, thenringcentral_list_queue_members"Show recent inbound calls for extension X" / "get that call's recording" →
ringcentral_list_user_call_log/ringcentral_list_company_call_log, thenringcentral_get_call_recordingusing the call log entry'srecording.id
It follows the MSPbots Vendor MCP Service SOP: stateless, no stored credentials, per-request header authentication. All 13 tools are read-only.
Authentication
RingCentral's REST API uses the JWT bearer flow — a server-to-server grant with no user browser redirect. A JWT credential is generated in the RingCentral admin console for a dedicated "service user" (Roles & Permissions → the service user's JWT credential), then exchanged for a short-lived access token:
POST https://platform.ringcentral.com/restapi/oauth/token
Authorization: Basic base64(client_id:client_secret)
Content-Type: application/x-www-form-urlencoded
grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer&assertion=<jwt>A fresh access token is cheap to obtain and this service must stay stateless, so it re-authenticates on every call rather than caching/refreshing a token — no derived token is ever cached across requests (SOP §3.4).
Credentials are read from HTTP headers only, on every request — never from environment variables. There is no local/single-tenant fallback mode; this keeps one tenant's credentials from ever leaking into another tenant's request.
Authentication headers
Every request to /mcp must include the following HTTP headers:
Header | Type | Required | Default | Allowed values | Description | Example |
| string | Yes | None | None | Client ID of the RingCentral App (an app registered in the RingCentral developer console) |
|
| string | Yes | None | None | Client Secret of the RingCentral App |
|
| string | Yes | None | None | JWT credential bound to a Service User (generated under Roles & Permissions in the RingCentral admin console); this service exchanges it for a short-lived access token and never stores it on disk |
|
Missing any of the three headers returns 401 Unauthorized with a required_headers list in the body.
Quick Start
Docker (recommended)
docker compose up --buildThe server starts on http://localhost:8080.
Local (uv)
uv sync
python -m ringcentral_mcpHealth Check
curl http://localhost:8080/health
# {"status": "ok"}No credentials are required for the health endpoint (it is a pure local liveness probe and never calls the RingCentral API).
Environment Variables
Variable | Default | Description |
|
| Listening port |
|
| Listening host |
No credential fields exist in configuration — see Authentication above.
MCP Endpoint
POST http://localhost:8080/mcpConnect your MCP client with:
Transport:
http(Streamable HTTP)Headers:
X-RingCentral-Client-Id,X-RingCentral-Client-Secret,X-RingCentral-Jwt(all required)
Available Tools (13)
Tool | Description | Parameters | API |
| Get basic company/account information for the current account | None |
|
| List the extensions under the account (users/queues/departments) |
|
|
| Get a single extension's details |
|
|
| List company and extension phone numbers |
|
|
| Get an extension's online/on-call/do-not-disturb status |
|
|
| List call queues |
|
|
| List the members of a call queue |
|
|
| List the company directory (internal users) |
|
|
| List the personal address book contacts of an extension |
|
|
| List the company-wide call log |
|
|
| List a single extension's call log |
|
|
| Get recording metadata (including the contentUri used for download) |
|
|
| Get the recording media's content-type/size (without the audio itself) |
|
|
page/per_page on list tools: this server caps per_page at 200 regardless of the higher limits some RingCentral endpoints document (call-log endpoints allow up to 1000, directory/entries up to 2000) — 200 is the stricter of "our SOP ceiling" vs. "vendor's real max" in every case here, so 200 always governs. per_page is otherwise passed straight through to RingCentral's own perPage query parameter.
Test Example
{
"method": "tools/call",
"params": { "name": "ringcentral_list_extensions", "arguments": {} }
}Equivalent curl against the running server (streamable HTTP MCP endpoint):
curl -X POST http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "X-RingCentral-Client-Id: <client_id>" \
-H "X-RingCentral-Client-Secret: <client_secret>" \
-H "X-RingCentral-Jwt: <jwt>" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": { "name": "ringcentral_list_extensions", "arguments": {} }
}'API Reference
Per-page limits verified against RingCentral's own OpenAPI spec (
assets-developers.ringcentral.com/dpw/api-reference/specs/public/office/rc-platform.yml): the genericperPageparameter (extensions, phone numbers, queues, queue members, contacts) has no documented maximum; call-log endpoints document a documented max of 1000;directory/entriesdocuments a max of 2000. This server's own 200 hard cap is stricter than all of these, so it is always the binding limit.
Known Gaps / Implementation Notes
⚠️ Not yet tested against a live RingCentral account. All 13 tools have been checked structurally only (MCP handshake, tools-list, schema validity,
/health, gateway 401 credential-gating). Per the parent ClickUp task, this is currently blocked at the business/procurement level — MSPbots has never purchased a RingCentral service (no paid user seat), and a JWT credential can only be bound to a real service user account, so no test credentials are available yet.Endpoints verified directly against RingCentral's official OpenAPI spec — not guessed.
ringcentral_get_call_recording/ringcentral_download_call_recording: there is no standalone "list all recordings" endpoint — recording IDs must come from a call-log entry'srecording.idfield (query call logs withrecordingType/withRecordingparams to surface them).ringcentral_download_call_recordingcannot return actual audio bytes (not representable as MCP tool text output) — it returns content-type/size only; useringcentral_get_call_recording'scontentUrifield for an actual download URL."Queues" have no separate
/call-queueresource type in RingCentral's model — they're extensions with type Department/Call Queue, exposed at the dedicated/call-queuespaths used here.Scope is limited to the 13 operations above, not RingCentral's full API surface (which also includes messaging/SMS, meetings, fax, call control/RingOut, and account provisioning).
This server only runs in HTTP/gateway mode (no stdio transport, no single-tenant env-var credential mode) — the SOP requires credentials to come exclusively from per-request headers, so a code path that reads them from the environment instead was removed rather than kept as a "local dev convenience."
Available Tools
13 toolsringcentral_download_call_recordingA
Download a call recording's media content (returns metadata about the binary — content type and size — not the raw audio bytes, which aren't representable as MCP tool output).
API: GET /restapi/v1.0/account/~/recording/{recordingId}/content
(served from the media.ringcentral.com host, not the platform API host)
Args:
recording_id: Required. The recording ID (from a call-log entry's `recording.id` field).
Inputs: recording_id (required). Returns: result
ringcentral_get_account_infoA
Get basic company/account information for the current account.
API: GET /restapi/v1.0/account/~
Inputs: no named parameters. Returns: result
ringcentral_get_call_recordingA
Get a call recording's metadata (returns a content URI, not the audio itself).
API: GET /restapi/v1.0/account/~/recording/{recordingId}
Args:
recording_id: Required. The recording ID (from a call-log entry's `recording.id` field).
Inputs: recording_id (required). Returns: result
ringcentral_get_extensionA
Get a single extension's details.
API: GET /restapi/v1.0/account/~/extension/{extensionId}
Args:
extension_id: The extension ID, or "~" for the currently authenticated extension (default).
Inputs: extension_id. Returns: result
ringcentral_get_presenceA
Get an extension's presence/telephony/do-not-disturb status.
API: GET /restapi/v1.0/account/~/extension/{extensionId}/presence
Args:
extension_id: The extension ID, or "~" for the currently authenticated extension (default).
Inputs: extension_id. Returns: result
ringcentral_list_company_call_logA
List account-wide call log records.
API: GET /restapi/v1.0/account/~/call-log
Args:
date_from: ISO 8601 start of the date range.
date_to: ISO 8601 end of the date range.
view: "Simple" or "Detailed".
direction: "Inbound" or "Outbound".
type: Call type, e.g. "Voice", "Fax".
page: Page number.
per_page: Results per page (max 1000).
Inputs: page, type, view, date_to, +3 more. Returns: result
ringcentral_list_extensionsA
List extensions on the account.
API: GET /restapi/v1.0/account/~/extension
Args:
type: Filter by extension type, e.g. "User", "Department", "Announcement".
status: Filter by status, e.g. "Enabled", "Disabled", "NotActivated".
extension_number: Filter by extension number.
email: Filter by email address.
page: Page number.
per_page: Results per page.
Inputs: page, type, email, status, +2 more. Returns: result
ringcentral_list_external_contactsA
List an extension's personal address-book contacts.
API: GET /restapi/v1.0/account/~/extension/{extensionId}/address-book/contact
Args:
extension_id: The extension ID, or "~" for the currently authenticated extension (default).
starts_with: Filter to contacts whose name starts with this string.
phone_number: Filter by phone number.
page: Page number.
per_page: Results per page.
Inputs: page, per_page, starts_with, extension_id, +1 more. Returns: result
ringcentral_list_internal_contactsA
List internal company directory entries (corporate users/extensions).
API: GET /restapi/v1.0/account/~/directory/entries
Args:
type: Filter by directory entry type.
site_id: Filter by site ID (for multi-site accounts).
page: Page number.
per_page: Results per page.
Inputs: page, type, site_id, per_page. Returns: result
ringcentral_list_phone_numbersA
List all company and extension phone numbers.
API: GET /restapi/v1.0/account/~/phone-number
Args:
usage_type: Filter by usage type, e.g. "DirectNumber", "CompanyNumber".
status: Filter by status, e.g. "Normal", "Reserved".
page: Page number.
per_page: Results per page.
Inputs: page, status, per_page, usage_type. Returns: result
ringcentral_list_queue_membersA
List the members of a call queue.
API: GET /restapi/v1.0/account/~/call-queues/{groupId}/members
Args:
queue_id: Required. The call queue's extension ID.
page: Page number.
per_page: Results per page.
Inputs: queue_id (required), page, per_page. Returns: result
ringcentral_list_queuesB
List call queues on the account.
API: GET /restapi/v1.0/account/~/call-queues
Args:
page: Page number.
per_page: Results per page.
Inputs: page, per_page. Returns: result
ringcentral_list_user_call_logA
List call log records for a specific extension/user.
API: GET /restapi/v1.0/account/~/extension/{extensionId}/call-log
Args:
extension_id: The extension ID, or "~" for the currently authenticated extension (default).
date_from: ISO 8601 start of the date range.
date_to: ISO 8601 end of the date range.
view: "Simple" or "Detailed".
direction: "Inbound" or "Outbound".
page: Page number.
per_page: Results per page (max 1000).
Inputs: page, view, date_to, per_page, +3 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 13 tools
Each tool targets a distinct resource and action (presence, account, extensions, queues, contacts, call logs, recordings). The only minor overlap is between ringcentral_list_extensions and ringcentral_list_internal_contacts, but their descriptions clearly differentiate account extensions from directory entries.
All tools follow a consistent ringcentral_<verb>_<resource> pattern, using 'get' for single items and 'list' for collections. The naming is uniformly snake_case and predictable, making it easy to infer the purpose of each tool.
Thirteen tools is well-scoped for a RingCentral API server covering account info, extensions, contacts, call logs, and recordings. Each tool has a clear purpose and none feel redundant; the count is in the ideal range for a domain-specific MCP server.
The surface covers the main read-only resources: presence, account, extensions, phone numbers, queues, contacts, and call logs/recordings. Minor gaps like missing single-phone-number lookup or queue detail endpoints are workable, as the list tools provide sufficient data for most queries.
Maintenance
Related MCP Connectors
One OAuth connector for your team's remote MCP servers, with Tool Packs, guardrails and logs.
Your team's custom tools and skills in every agent, through one MCP connection.
Discover, plan and run tools across your connected business systems through one OAuth MCP endpoint
Create, schedule, and publish social posts, manage accounts, and read analytics as MCP tools.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables file system operations, web scraping, and AI-powered search through MCP tools for use by LLM agents.1-
- FlicenseNot gradedqualityCmaintenanceMCP server for Bvoip / 1Stream that exposes call-reporting, phone-status, and CRM-extension-mapping endpoints as MCP tools.-

Dial MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to provision phone numbers, send SMS, place AI voice calls, and react to inbound events via the Dial communication stack, all through MCP tools.219 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage and monitor a Five9 contact center, including campaigns, agents, IVR flows, call statistics, and reports through MCP.MIT