gtmmcps.
Tool record

RingCentral App Connect MCP documentation

Research date: 2026-09-07

Documentation coverage: partial.

Reference index, not a mirror of complete vendor documentation. Retrieved pages do not prove the MCP works.

What it does

One of four MCP servers RingCentral publishes through its Labs programme; this one bridges RingCentral telephony to whichever CRM the customer has linked through the App Connect browser extension, so an assistant can look up or create CRM contacts, log a call to the CRM and pull RingCentral call logs.

Access and connection

MCP support: official

Access requirements: paid - a RingCentral subscription is required and the Labs MCP servers carry no separate price. The vendor's plans and pricing page states "RingCentral provides a suite of powerful APIs for voice, SMS/MMS, team messaging, video, fax, data management and system configuration." Per-seat prices on that page are rendered client-side and were not captured by this fetch, so no figure is recorded here.

Authentication: oauth plus a second, separate CRM link. The docs describe a two-layer model: RingCentral identity via OAuth 2.0 or SSO established when the server is added to the AI client, and then a CRM connection linked through the App Connect Chrome extension rather than inside the AI client, with only one CRM connected per RingCentral account at a time.

Research checked: 2026-09-07

These details come from the catalog research. Check the vendor sources below for current setup instructions. They do not establish that a connection or tool call was tested.

Sources

Retrieved pages

Markdown JSON