Connect a client
Get your MCP URL and wire it into Claude or ChatGPT
Tool reference
Every tool, its inputs and what it returns
What the assistant can do
Architecture
The MCP server runs inside the Ringee backend. There is nothing extra to deploy. Every tool call resolves to the same domain services the dashboard uses, so permissions, credit rules and workspace scoping behave identically no matter where the request comes from.Two endpoints, two auth models
Workspace scoping
Everything an assistant reads or writes is scoped to the active workspace — your personal account or one organization. The assistant can move between them withswitch_workspace, with no re-authentication. See Workspaces.
Safety model
Tools are annotated with the MCP trust hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) so clients can warn before something consequential happens.
- Destructive tools —
delete_contact,delete_call_session— require explicit confirmation, anddelete_contactadditionally requires the contact’s stored phone number. - Sensitive tools —
reveal_lead,create_call_session— spend provider credits or mint shareable links. - MCP lead tools never spend Ringee credits, though
search_leadsandreveal_leaddo consume your connected enrichment provider’s allowance.
Beyond the raw protocol
ringee CLI
Drive the same tools from a terminal or a shell-capable agent
Claude skills
/ringee commands in Claude Code and claude.aiChatGPT app
Visual Ringee cards inside ChatGPT
Next steps
Connect your first client
Get your MCP URL from the dashboard and paste it into Claude

