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)

Scope

13 tools, aligned to MSPbots' historical usage categories (Account Info, Extension, Phone Numbers, Presence, Queues, Queue Members, Internal Contacts, External Contacts, Company Call Log Records, User Call Log Records, Call Recording).

Related MCP server: Sentinel Core Agent

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>

The response includes both an access token and a refresh token, but since re-exchanging the JWT itself is cheap and this service must stay stateless, it re-authenticates on every call rather than caching/refreshing.

Quick Start

cd D:\claude\project\ringcentral-mcp
uv sync

$env:RINGCENTRAL_CLIENT_ID="your_app_client_id"
$env:RINGCENTRAL_CLIENT_SECRET="your_app_client_secret"
$env:RINGCENTRAL_JWT="your_service_user_jwt_credential"
uv run ringcentral-mcp

Configuration

Copy .env.example to .env and fill in your values:

HEADER 授权参数说明

Claude Desktop Setup

{
  "mcpServers": {
    "ringcentral": {
      "command": "uv",
      "args": ["run", "--directory", "D:/claude/project/ringcentral-mcp", "ringcentral-mcp"],
      "env": {
        "RINGCENTRAL_CLIENT_ID": "your_app_client_id",
        "RINGCENTRAL_CLIENT_SECRET": "your_app_client_secret",
        "RINGCENTRAL_JWT": "your_service_user_jwt_credential"
      }
    }
  }
}

Transport Modes

stdio

$env:RINGCENTRAL_CLIENT_ID="your_app_client_id"
$env:RINGCENTRAL_CLIENT_SECRET="your_app_client_secret"
$env:RINGCENTRAL_JWT="your_service_user_jwt_credential"
uv run ringcentral-mcp

HTTP — single-tenant

$env:RINGCENTRAL_CLIENT_ID="your_app_client_id"
$env:RINGCENTRAL_CLIENT_SECRET="your_app_client_secret"
$env:RINGCENTRAL_JWT="your_service_user_jwt_credential"
$env:MCP_TRANSPORT="http"
$env:AUTH_MODE="env"
uv run ringcentral-mcp

HTTP — gateway / multi-tenant

$env:MCP_TRANSPORT="http"
$env:AUTH_MODE="gateway"
uv run ringcentral-mcp
# Each request must include: X-RingCentral-Client-Id, X-RingCentral-Client-Secret, X-RingCentral-Jwt headers

Available Tools (13)

Known Gaps

• ⚠️ 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 (assets-developers.ringcentral.com/dpw/api-reference/specs/public/office/rc-platform.yml, linked from the developer docs site) — 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's recording.id field (query call logs with recordingType/withRecording params to surface them).

• "Queues" have no separate /call-queue resource type in RingCentral's model — they're extensions with type Department/Call Queue, exposed at the dedicated /call-queues paths 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).

API Reference

• RingCentral API Reference

• JWT Auth Flow