RingCentral

RingCentral

This connector works with one RingCentral (RingEX) account through the RingCentral REST API (https://platform.ringcentral.com/restapi/v1.0), signed in as the RingCentral user who authorizes it: account and extensions, the company directory, the user's phone numbers, call log (own and, for admins, the whole company), active calls, RingOut calls, SMS and the message store (texts, voicemails, faxes) with attachments, the personal address book, presence, and RingCentral Video meetings.

Setup (about 10 minutes)

1. Sign in at https://developers.ringcentral.com/console with your RingCentral account and click Register App, type REST API App.
2. Under Auth, choose 3-legged OAuth flow authorization code and Server-side web app (it keeps a client secret). Under OAuth Redirect URI enter https://cloud.anythingmcp.com/api/mcp-oauth/callback on AnythingMCP Cloud, or <your AnythingMCP URL>/api/mcp-oauth/callback when you host AnythingMCP yourself.
3. Under Security, Application Scopes, select the permissions the tools need: Read Accounts, Read Call Log, Read Messages, Edit Messages, SMS, RingOut, Read Contacts, Contacts, Read Presence, Edit Presence and Video. RingCentral takes the permissions from the app, not from the sign-in request, so a permission you leave out makes those tools answer 403.
4. Create the app and copy the Client ID and Client Secret (Credentials) into RINGCENTRAL_CLIENT_ID and RINGCENTRAL_CLIENT_SECRET.
5. Install, then click Authorize with Provider on the connector page and sign in with the RingCentral user the AI should act as. Run ringcentral_get_my_extension to check.

Environment: everything runs against production, platform.ringcentral.com. RingCentral retired its developer sandbox (platform.devtest.ringcentral.com) at the end of 2024; the host no longer exists. Test with your normal account or a separate RingEX account. Apps no longer need graduation: the credentials in the console are production credentials.

Sign-in lifetime: an access token lasts one hour and is renewed automatically with the refresh token. RingCentral refresh tokens expire after 7 days by default and each renewal hands out a new one, so a connector that is not used for more than a week has to be authorized again.

Calls and texts reach real people: ringcentral_ringout_call places a call and ringcentral_send_sms sends a text; both can cost money. In the US, business texting requires a registered sender (10DLC campaign or verified toll-free number) and the recipient's consent. Show the user the numbers and the text and act only after a clear yes. ringcentral_cancel_ringout, ringcentral_update_presence, ringcentral_create_contact, ringcentral_update_contact, ringcentral_mark_message and ringcentral_create_video_meeting change data; confirm them too.

Workflow

• Who and where: ringcentral_get_my_extension, ringcentral_get_account, ringcentral_list_extensions, ringcentral_get_extension, ringcentral_search_directory, ringcentral_list_my_phone_numbers (the SMS-capable numbers have the SmsSender feature).
• Calls: ringcentral_list_call_log (own) or ringcentral_list_company_call_log (admin), ringcentral_get_call_record, ringcentral_list_active_calls. Place a call with ringcentral_ringout_call, follow it with ringcentral_get_ringout_status, stop it with ringcentral_cancel_ringout.
• Texts, voicemail and fax: ringcentral_list_messages (message_type SMS, VoiceMail or Fax; distinct_conversations for an inbox), ringcentral_get_message, ringcentral_get_message_attachment for the audio, the fax document or the voicemail transcription, ringcentral_mark_message. Send a text with ringcentral_send_sms. Sending faxes is not part of this connector.
• Contacts: ringcentral_list_contacts, ringcentral_get_contact, ringcentral_create_contact, ringcentral_update_contact.
• Availability: ringcentral_get_presence, ringcentral_list_presence, ringcentral_update_presence.
• Video: ringcentral_list_video_meetings, ringcentral_get_video_meeting, ringcentral_create_video_meeting.

Reading the answers: ~ in a path means the signed-in account or user. Ids are numeric strings. Times are ISO 8601 in UTC (2026-10-30T14:05:00.000Z); call duration is in seconds; video startTime / endTime filters are Unix milliseconds. Phone numbers are E.164 (+14155550123); the call log phone_number filter takes the digits without the plus. In the message store subject holds the SMS text. A call result such as Missed, Voicemail, Accepted or Call connected says how it ended.

Paging: list answers carry records and paging (page, perPage, totalPages, totalElements); pass page for the next one. Call log and message store default to the last 24 hours: set date_from for older items. Video history pages with page_token (paging.nextPageToken).

Limits and errors: RingCentral limits each user and app per minute by API group: Light 50, Medium 40, Heavy 10 requests (call log, active calls, presence of all users, directory search, contacts and RingOut are Heavy). A 429 means wait about a minute. 401 means the sign-in expired (authorize again); 403 with InsufficientPermissions means the app lacks the permission (add it under Application Scopes and authorize again) or the user lacks the role, for example for the company call log; 404 an unknown id; 400 or CMN-101 an invalid number or parameter; FeatureNotAvailable means the number cannot send SMS.