Connect your account, then chat with AI to run tools.
Pull call history, queues, and extension settings from chat — update forwarding, blocking, and business hours without opening the admin console.
Live probe refreshed Sep 14, 2026 · Endpoint host mcp.mcpbundles.com
Built for
IT Administrators, Operations Managers, Customer Support Leads, Revenue Operations Teams
Call history audit
Common support QA workflow — extension-scoped call log read.
Pull RingCentral call records for the last week for my extension — summarize inbound vs outbound, total duration, and missed calls.
Connect RingCentral to any MCP client in minutes
You’ll sign in to MCPBundles when your client connects.
https://mcp.mcpbundles.com/bundle/ringcentralThis server needs a sign-in. MCPBundles handles that setup once — then chat here with saved access and a log of what ran.
Opens MCPBundles Studio with this server selected. After sign-in, chat and run tools from the same thread.
Browse all toolsQueue inventory
Company-level read before queue or routing changes.
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.
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.
Add a mobile forwarding number +14155550123 labeled Mobile to my RingCentral extension.
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.
Domain knowledge for RingCentral — workflow patterns, data models, and gotchas for your AI agent.
RingCentral organizes telephony under Account and Extension (user/line). Company-level settings (queues, business hours) and extension-level settings (forwarding, call blocking) are separate.
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.
Showing 25 of 27 from the live probe.
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 to use the JWT user's extension.
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 queue. Requires ReadAccounts on your REST API app.
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 REST API app. Omit extension_id to use the JWT user's extension.
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, extensionNumber, name, and type. Resolve extension ids here before extension-scoped reads.
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. Omit extension_id to use the JWT user's extension.
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 extensions and monitoring permissions.
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. Omit extension_id to use the JWT user's extension.
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 caller-blocking API. Omit extension_id to use the JWT user's extension.
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 on extension type — the upstream API validates contact and type payloads.
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 update. Omit extension_id to use the JWT user's extension.
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.
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.
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.
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.
RingCentral provides 28 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.
RingCentral uses API Key. RingCentral requires credentials. Connect via MCPBundles and authentication is handled automatically.
© 2026 ThinkChain Inc. All rights reserved.
MCPBundles is an independent platform built on the open Model Context Protocol standard. Not affiliated with Anthropic PBC or Claude.
Other MCP servers in this category from the directory index
Notion's official MCP server providing direct access to workspaces, pages, databases, blocks, and co...
Jam is a collaborative bug reporting and feedback tool that allows teams to capture, annotate, and s...
This server serves as the remote API for Guru, a knowledge management tool, but lacks specific detai...
Fireflies is an AI-powered meeting assistant that automatically records, transcribes, and analyzes v...
This server provides event organizers with a suite of tools to manage interactions with attendees an...
Official Airtable MCP server providing AI-powered access to Airtable bases, tables, records, and sch...