Skip to main content
Glama
MSPbotsAI

ringcentral-mcp

by MSPbotsAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AUTH_MODENogateway = credentials per-request via headers (SOP-compliant); env = shared credentials from env vars (local dev only)gateway
MCP_HTTP_PORTNoHTTP server port8080
MCP_TRANSPORTNostdio (Claude Desktop) or http (gateway)stdio
RINGCENTRAL_JWTNoJWT credential issued to a service user
RINGCENTRAL_CLIENT_IDNoRingCentral app's client ID
RINGCENTRAL_CLIENT_SECRETNoRingCentral app's client secret

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
ringcentral_get_account_infoA

Get basic company/account information for the current account.

    API: GET /restapi/v1.0/account/~
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.
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).
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.
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).
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.
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.
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.
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.
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).
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).
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).
ringcentral_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).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 13 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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

ActivityMaintained
ResponsivenessNo issues

Resources