For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.mcpbundles.com/bundle/ringcentral
Skill page: https://www.mcpbundles.com/skills/ringcentral
Tools: 46
Live probe refreshed Nov 21, 2026 · Endpoint host mcp.mcpbundles.com
What you can do with RingCentral
Built for
IT Administrators, Operations Managers, Customer Support Leads, Revenue Operations Teams
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms
RingCentral
Add to your AI client, then sign in once when you connect.
Pull call history, queues, and extension settings from chat — update forwarding, blocking, and business hours without opening the admin console.
This listing identifies a third-party integration. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
Best forIT AdministratorsOperations ManagersCustomer Support LeadsRevenue Operations
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
Account extensions — read extensions for the account (use ~ for the authenticated account) and take each row's id before any extension-scoped call.
Extension-scoped reads — forwarding numbers, caller blocking, business hours, active calls, call history, message store, and personal contacts per extension.
Directory search — company directory lookup by name, extension, phone, or email (account-scoped POST).
Admin reads — sites, account phone numbers, audit trail search, user roles, and presence.
Media downloads — call recording audio and message attachments spill to presigned links when large.
AI insights — RingSense transcript and summary reads use recording or telephony session ids from call log.
Writes — confirm ids from reads first. SMS, presence, and phone-number assign are high-impact; legacy extension, queue, and routing writes remain available where noted in tool copy.
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 Records — call history and CDR data; filter lists with ISO date ranges.
Message Store — SMS, voicemail, fax, and pager mailbox messages.
Directory — company people and lines (search); Contacts — personal address book per extension.
Call Recordings — metadata for recorded calls (ids come from call log rows).
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, directory search, sites, and phone numbers need ReadAccounts; call logs need ReadCallLog; message store needs ReadMessages; personal contacts need ReadContacts; recording metadata and audio downloads need ReadCallRecording; presence read needs ReadPresence, presence write needs EditPresence; audit search needs ReadAuditTrail; AI insights need RingSense; SMS send needs SMS scope. Phone-number assign uses REST v2 and needs EditAccounts.
Recording downloads: RingCentral throttles recording content — download one id at a time, not in tight loops.
Showing 46 of 46 tools from the public preview. Connect the server to inspect the full live tool list.
Ringcentral46
Ringcentral Assign Phone Number
write
ringcentral_assign_phone_number
Assign or reassign an account phone number to an extension or company usage. Uses RingCentral REST v2. Confirm phone_number_id and target extension REST id from phone number and extension reads first. Requires EditAccounts and EditCompanyPhoneNumbers. Misconfiguration can change company main numbers — verify usageType before calling.
Ringcentral Assign Phone Number — Assign or reassign an account phone number to an extension or company usage. Uses RingCentral REST v2. Confirm phone_number_id and target extension REST id from phone number and extension reads first. Requires EditAccounts and EditCompanyPhoneNumbers. Misconfiguration can change company main numbers — verify usageType before calling.
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 Download Call Recording — Download call recording audio for a recording id from call history. Returns inline base64 for small files or a presigned download link when larger. Requires ReadCallRecording. RingCentral rate-limits recording downloads — fetch one recording at a time, not in bulk loops.
Ringcentral Download Message Attachment — Download voicemail audio, fax PDF, or MMS attachment bytes for a message store row. Use attachment id from a prior message read. Returns inline base64 for small files or a presigned download link when larger. Requires ReadMessages.
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.
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.
Standard connector25 free calls every 30 days, then from $19/month
$19 / month
Subject to fair usage limits
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 Recording — Read metadata for a call recording id from call history — content URI, MIME type, and duration. Requires ReadCallRecording on your REST API app. Download binary audio via the call recording download tool.
Ringcentral Get Call Records — Read call history for a user extension. Omit record_id to page through call logs with optional dateFrom, dateTo, direction, and type filters; pass record_id for one call record including recording metadata when present. 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 Contacts — Read personal address-book contacts for a user extension. Omit contact_id to list with pagination; pass contact_id for one contact. Requires ReadContacts or ReadPersonalContacts on your REST API app. Omit extension_id for the JWT user.
Ringcentral Get Extension Phone Numbers — Read phone numbers mapped to a user extension, including SMS-capable lines (check features for SmsSender before sending SMS). Omit extension_id for the JWT user's extension. Requires ReadAccounts.
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 Messages — Read SMS, voicemail, fax, and pager messages from an extension mailbox. Omit message_id to list with filters; pass message_id for one message including attachment metadata. Requires ReadMessages on your REST API app. Omit extension_id to use the JWT user's extension.
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 My Extension — Read the authenticated JWT user's extension profile — numbers, name, type, and status. Use this before extension-scoped comms reads when you need the current user's line without listing every account extension.
Showing the first 25 tools — full list and schemas: Directory API.
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 46 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.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.
More in collaboration
Other MCP servers in this category from the directory index