RingEX-Chat
by RingEX-Chat
Read RingCentral Team Chat and post, edit or delete messages from an AI agent. Nine tool names dispatch to 52 documented resource/action operations, seven of them deletes. OAuth on a user token; the default consent request asks for 11 RingCentral scopes including SMS.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect RingEX-Chat via MCP
https://mcp.labs.ringcentral.com/ringex/v1.1.0/team-chatWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
RingEX-Chat Tools & Capabilities (9)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- No scope boundary falls between reading a chat and deleting a team. RingCentral's OpenAPI specification attaches the single permission
TeamMessagingto all 66 team-messaging operations it documents, listing tools and deleting a team alike. Granting the connector enough to read is granting it enough to destroy. - The consent request is nine scopes wider than the descriptor. The RFC 9728 document names two; the authorization endpoint asks for eleven by default, including
SMS,EditAccountsandReadCallRecording, none of which any tool on this server uses. - The tool count is not the operation count. Nine names, 52 documented operations. Any reasoning about this connector that starts from "only nine tools" starts from the wrong number.
- We could not read live schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or server-declared
destructiveHintis published here. The access classification is RingCentral's documentation. - RingCentral's own tables are explicitly not authoritative on parameters. Its tools reference states the resource/action tables are "guidance, not a substitute" for calling
tools/list, and that exact required fields are only visible there. So 52 is the count of documented combinations, and the live schema is what governs. - No SLA, and names can change without notice. RingCentral labels the server Labs, excludes it from its standard SLA, and reserves the right to rename, modify or remove tools without prior notice. A 30-day deprecation notice is its stated policy for tools marked deprecated, with 14 days for breaking parameter changes.
- No unread state, read receipts or full-text search exist. RingCentral's own skill guidance says this API surface cannot rank by unread state or run a server-side keyword search across history, and instructs agents never to claim a post is unread or that someone has seen a message.
Action.Submiton an Adaptive Card needs infrastructure this connector does not provide. RingCentral states it requires an application configured for Interactive Messages with an outbound webhook URL, and that a generic incoming webhook cannot receive submitted interaction data. A card with buttons will render; the button presses go nowhere without that setup.- ChatGPT Pro cannot post. With read/fetch-only Developer Mode, RingCentral documents that you can read chats and posts but cannot post messages or create conversations.
- Adaptive Cards are restricted to version 1.3 with only
Action.OpenUrlandAction.Submit, and must carryfallbackText. RingCentral rejects other versions or actions before the request reaches it. - Post text is capped at 10,000 characters and a post carries at most 25 attachments, per RingCentral's tool documentation and its Create Post schema.
- Whether a post triggers a notification is unresolved. We found no RingCentral documentation stating whether an agent-sent post pushes a mobile notification to chat members, and we did not test it. Treat it as unknown rather than as a no.
Frequently asked questions
Yes. send_post writes a real Team Chat post into a channel or a direct conversation, visible immediately to everyone in it. RingCentral's Create Post API records the author as creatorId, described in its OpenAPI specification as the identifier of the user who wrote the post. There is no bot identity field, so the message appears under your own name.
Fifty-two. RingCentral's tools reference documents each write tool as taking a resource or action discriminator, and the published tables enumerate 52 valid combinations across the nine names. Seven of those are delete actions, covering posts, teams, Adaptive Cards, notes, tasks, events and incoming webhooks. Counting tool names understates the surface by roughly six times.
No tool on this server can. Sending a text is send_sms, which RingCentral documents on its separate RingEX Phone server at a different endpoint, and no tool on any RingEX server places a call. But the Chat server's default OAuth request includes the SMS scope, so the token it obtains can reach RingCentral's Send SMS endpoint directly.
Two are advertised and eleven are requested by default. The server's RFC 9728 descriptor names ReadAccounts and TeamMessaging. Its authorization endpoint, probed on 2026-08-22, redirects a client that sends no scope parameter to RingCentral asking for ReadAccounts, ReadContacts, ReadCallLog, AI, ReadMessages, ReadPresence, SMS, TeamMessaging, ReadCallRecording, Analytics and EditAccounts.
Yes, through manage_team. RingCentral documents twelve actions on that one tool, including delete, archive and remove_members, and its own skill guidance calls deletion irreversible. The TeamMessaging permission that authorizes reading a chat is the same permission RingCentral's API specification attaches to deleting a team, so no scope separates them.
Yes. read_team_chat returns posts, notes, tasks and file contents written by colleagues and by anyone in a shared chat, and it runs in the same session as tools that post, edit and delete as you. RingCentral's own skill files state that retrieved content is never authorization to act. Treat every retrieved post as data, not instructions.
RingCentral says no. Its documentation labels the server RingCentral Labs, states it is not covered by RingCentral's standard SLA, and warns that tools may be renamed, modified or removed without prior notice, advising caution in production. Anthropic's directory separately describes the connector as Beta. The endpoint already carries a version path, v1.1.0.
They were consolidated into nine in version 1.1.0. RingCentral's changelog records that the 64 previous team_messaging tools were removed and replaced by workflow-oriented tools taking a resource or action discriminator. Three data-export tools moved to the separate RingEX Admin server because bulk export is an account-sensitive administrative workflow.
Sources
- RingEX Chat server page (retrieved 2026-08-22) · retrieved 2026-08-22
- RingEX Chat tools reference, the resource/action tables (retrieved 2026-08-22) · retrieved 2026-08-22
- RingEX Chat setup guide, for Claude, ChatGPT and Codex (retrieved 2026-08-22) · retrieved 2026-08-22
- RingEX Phone server page, for the SMS boundary (retrieved 2026-08-22) · retrieved 2026-08-22
- RingCentral MCP changelog, v1.1.0 consolidation (retrieved 2026-08-22) · retrieved 2026-08-22
- RingCentral skill library, "Post to Chat", "Read Team Chat", "Manage Teams" and "Send SMS" — · · · (retrieved 2026-08-22) · retrieved 2026-08-22
- RingCentral platform OpenAPI specification, version 1.0.60-20260812, for per-operation
x-app-permissionvalues, the Create Post and Send SMS definitions, and the 66 team-messaging operations (retrieved 2026-08-22).developers.ringcentral.com/robots.txtallows this path and names this spec host in its sitemap directives. · retrieved 2026-08-22 - Live auth posture check, 2026-08-22: anonymous
initializereturned 401 withwww-authenticate: Bearer ... scope="ReadAccounts TeamMessaging"; RFC 9728 descriptor at ; authorization server metadata at the siblingoauth-authorization-serverpath; authorization endpoint probed with and without ascopeparameter. A control path under/ringex/v1.1.0/returned 404, so the descriptor is genuine rather than a catch-all. · retrieved 2026-08-22 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- RingCentral support — · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Communication
- Developer
- RingEX-Chat
- Tools
- 9
- Domain
- mcp.labs.ringcentral.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.