Skip to content
Custom Connectors

Connect RingCentral to Claude Code

Let Claude send texts and place calls from your RingCentral number. From the terminal, inside the sessions where you already work.

How do you connect RingCentral to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect RingCentral, you add a RingCentral MCP server: a small hosted service that exposes RingCentral's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own RingCentral account. No API keys pasted into config files.

claude mcp add --transport http ringcentral https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in RingCentral once connected?

Full read-write RingCentral access lets Claude send an SMS from your business number, post into a team chat, trigger a RingOut call, look up and update contacts, and pull call records for follow-up. The messaging and call handling that used to mean switching apps happen where the conversation already lives, once you approve.

  • Send an SMS from your business number to a contact after you approve
  • Post a message into a RingCentral team chat or group
  • Trigger an outbound RingOut call to connect two numbers
  • Look up call logs and recordings for a number and summarize them
  • Create or update a contact record in the address book
  • Send or retrieve a fax tied to the account

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same RingCentral access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the RingCentral API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when RingCentral changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build RingCentral connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same RingCentral connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own RingCentral account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on RingCentral's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to RingCentral?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the RingCentral account it signs in with. Revoking access is one click in RingCentral.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.