What you can do with RingCentral

Built for

IT Administrators, Operations Managers, Customer Support Leads, Revenue Operations Teams

Example workflows

Call history audit

Common support QA workflow — extension-scoped call log read.

Try this

Pull RingCentral call records for the last week for my extension — summarize inbound vs outbound, total duration, and missed calls.

Queue inventory

Company-level read before queue or routing changes.

Try this

List RingCentral call queues on my account with member extension ids and queue names.

Extension directory

Foundation read — resolves REST ids for extension-scoped tools.

Try this

Read all RingCentral account extensions and return id, extensionNumber, name, and type in a table.

Update forwarding

Shows upsert create semantics on extension-scoped writes.

Try this

Add a mobile forwarding number +14155550123 labeled Mobile to my RingCentral extension.

Context to know first

What can AI agents do with RingCentral on MCPBundles?

Agents can read extensions, call queues, call logs, forwarding numbers, blocking settings, business hours, IVR prompts, and related account configuration. They can also create or update extensions, forwarding numbers, blocked numbers, business hours, call queues, and call handling rules when your REST app grants the required permissions.

How does RingCentral authentication work on MCPBundles?

Connect with a JWT credential plus your private REST API app's client id and client secret from the RingCentral Developer Console. MCPBundles exchanges the JWT for a fresh access token on each API call.

Why do agents need extension REST ids?

RingCentral extension-scoped APIs key off internal REST ids, not dialable extension numbers like 101. Read account extensions first and pass each row's id field — or omit extension_id to default to the JWT user's line.

AI Skill
SKILL.md

Domain knowledge for RingCentral — workflow patterns, data models, and gotchas for your AI agent.

RingCentral

RingCentral organizes telephony under Account and Extension (user/line). Company-level settings (queues, business hours) and extension-level settings (forwarding, call blocking) are separate.

Operational order

  1. Account extensions — read extensions for the account (use ~ for the authenticated account) and take each row's id before any extension-scoped call.
  2. Company-level reads — call queues, monitoring groups, business hours, call handling rules, call recording settings.
  3. Extension-scoped reads — forwarding numbers, caller blocking, business hours, active calls, call history per extension.
  4. Writes — only after confirming the target extension or queue id from a read. Extensions, forwarding numbers, blocked numbers, business hours, call queues, and handling rules support create/update/delete where noted in tool copy; dictionary assets (fax cover, IVR prompts), monitoring groups, and active calls are read-only upstream.

Data model

  • Account — organization; contains extensions and company settings.
  • Extension — user or phone line; has call handling, forwarding, business hours.
  • Call Queues — hunt groups for incoming calls.
  • Call Monitoring Groups — supervisor groups for monitoring agents (read-only).
  • Business Hours — when calls are routed; company and per-extension.
  • Call Handling Rules — routing rules (forward, voicemail, etc.).
  • Blocked/Allowed Numbers — per-extension allow/deny lists.
  • Call Records — call history and CDR data.
  • IVR Prompts — auto-attendant audio from the dictionary (list-only).
  • Fax Cover — fax cover page templates from the dictionary (list-only).

Tool shape

Reads collapse list and single fetch: omit resource ids to page, pass ids from prior rows for one record. Dictionary reads paginate only. Writes use upsert semantics (omit id to create, pass id to update) and explicit delete tools for destructive removes.

Gotchas

  • Read extensions before extension-scoped calls: The REST id is not the dialable extension number.
  • Default extension: Omit extension_id (or pass ~) to use the authenticated user's own extension on call-log and related tools.
  • Never pass extensionNumber: Values like 101 or 46 are dialable numbers, not REST ids — read account extensions and use each row's id.
  • account_id and extension_id: Most operations need account_id; extension-scoped reads also accept extension_id. Use ~ for the authenticated account or extension when appropriate.
  • REST app permissions: Call queues need ReadAccounts; per-extension call logs need ReadCallLog. Writes need the matching edit scopes on the private REST app (for example extension settings, call handling, or queue admin).

Tools in this Server (27)

Ringcentral Delete Blocked Number

Remove a blocked or allowed phone number entry from a user extension. Omit extension_id to use the JWT user's extension.

Ringcentral Delete Extension

Delete a RingCentral extension by REST id. This is destructive — confirm the extension id from an account extension read first.

Ringcentral Delete Forwarding Number

Remove a call forwarding number from a user extension. Omit extension_id to use the JWT user's extension.

Ringcentral Delete Handling Rule

Delete a company-level answering rule by id. Confirm the rule id from a company call handling rules read first.

Ringcentral Get Active Calls

Read currently active calls for a user extension. The upstream API exposes list-only access — omit extension_id to use the JWT user's extension.

Ringcentral Get Blocked Numbers

Read blocked or allowed phone numbers for a user extension. Omit phone_number_id to list entries; pass phone_number_id for one row. Omit extension_id ...

Ringcentral Get Callblock Settings

Read call blocking settings for a user extension — block/allow modes and related preferences. Omit extension_id to use the JWT user's extension.

Ringcentral Get Call Queues

Read call queues in a RingCentral account. Omit call_queue_id to list queues with pagination; pass call_queue_id (the queue extension id) for one queu...

Ringcentral Get Call Records

Read call history for a user extension. Omit record_id to page through call logs; pass record_id for one call record. Requires ReadCallLog on your RES...

Ringcentral Get Call Record Settings

Read account-level call recording settings including recording mode, call types recorded, and retention policy for the given account_id.

Ringcentral Get Company Business Hours

Read company-wide business hours for a RingCentral account including weekly schedules and holiday or special-hour exceptions.

Ringcentral Get Extensions

Read user and line extensions in a RingCentral account. Omit extension_id to page through extensions; pass extension_id for one extension row with id,...

Ringcentral Get Fax Cover Pages

Read available fax cover page templates from the RingCentral dictionary. The upstream API exposes list-only access — paginate with page and perPage.

Ringcentral Get Forwarding Numbers

Read call forwarding numbers for a user extension. Omit forwarding_number_id to list numbers with pagination; pass forwarding_number_id for one entry....

Ringcentral Get Handling Rules

Read company-level call handling rules. Omit rule_id to list rules with pagination; pass rule_id for one rule including conditions and actions.

Ringcentral Get Ivr Prompts

Read IVR greeting prompts from the RingCentral dictionary. The upstream API exposes list-only access — paginate with page and perPage.

Ringcentral Get Monitoring Groups

Read call monitoring groups in a RingCentral account. Omit group_id to list groups with pagination; pass group_id for one group including member exten...

Ringcentral Get User Business Hours

Read business hours configured for a user extension. Omit extension_id to use the JWT user's extension.

Ringcentral Upsert Blocked Number

Add or update a blocked or allowed phone number on a user extension. Omit phone_number_id to POST a new entry; pass phone_number_id to PUT an update. ...

Ringcentral Upsert Callblock Settings

Update call blocking settings for a user extension (modes, greetings, and related options). Pass the settings object fields documented by RingCentral ...

Ringcentral Upsert Call Queue

Update an existing call queue by its extension id. Pass queue configuration fields such as name, agents, or routing options in the settings object.

Ringcentral Upsert Call Record Settings

Update account-level call recording settings such as recording mode, call types to record, and retention policy.

Ringcentral Upsert Company Business Hours

Update company-wide business hours for a RingCentral account. Pass weekly schedules and optional intervals in the settings object.

Ringcentral Upsert Extension

Create or update a RingCentral extension. Omit extension_id to POST a new extension; pass extension_id to PUT an update. Required create fields depend...

Ringcentral Upsert Forwarding Number

Create or update a call forwarding number on a user extension. Omit forwarding_number_id to POST a new number; pass forwarding_number_id to PUT an upd...

Ringcentral Upsert Handling Rule

Create or update a company-level answering rule. Omit rule_id to POST a new rule; pass rule_id to PUT an update.

Ringcentral Upsert User Business Hours

Update business hours for a user extension. Pass weekly schedules in the settings object. Omit extension_id to use the JWT user's extension.

Frequently Asked Questions

What can AI agents do with RingCentral on MCPBundles?

Agents can read extensions, call queues, call logs, forwarding numbers, blocking settings, business hours, IVR prompts, and related account configuration. They can also create or update extensions, forwarding numbers, blocked numbers, business hours, call queues, and call handling rules when your REST app grants the required permissions.

How does RingCentral authentication work on MCPBundles?

Connect with a JWT credential plus your private REST API app's client id and client secret from the RingCentral Developer Console. MCPBundles exchanges the JWT for a fresh access token on each API call.

Why do agents need extension REST ids?

RingCentral extension-scoped APIs key off internal REST ids, not dialable extension numbers like 101. Read account extensions first and pass each row's id field — or omit extension_id to default to the JWT user's line.

How do I connect RingCentral to my AI agent?

Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/ringcentral. Authentication is handled automatically.

How many tools does RingCentral provide?

RingCentral provides 27 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.

What authentication does RingCentral require?

RingCentral uses API Key. RingCentral requires credentials. Connect via MCPBundles and authentication is handled automatically.

Setup Instructions

Connect RingCentral to any MCP client in minutes

MCP URL
https://mcp.mcpbundles.com/bundle/ringcentral

One-click install:

The link prefills the Add custom connector dialog — you still review the values and click Add, then Connect to complete OAuth.

Or add manually

  1. Open claude.ai → Settings → Connectors.
  2. Click the + button and choose Add custom connector.
  3. Set Name to RingCentral and paste the MCP URL into Remote MCP server URL.
  4. Click Add. RingCentral will appear under Not connected — select it and click Connect to complete OAuth.
Name: RingCentral
Remote MCP server URL: https://mcp.mcpbundles.com/bundle/ringcentral
Authentication: OAuth

Custom connectors at claude.ai require a paid Claude plan (Pro, Max, Team, or Enterprise).

Ready to use RingCentral?

Sign in to connect your credentials and start running tools from the chat.

RingCentral MCP Server — Phone System Ops for AI Agents