Model Context Protocol
RevDesk MCP server
Use RevDesk from ChatGPT, Codex, Claude, and other MCP clients to review calls and usage, manage phone numbers and caller IDs, send SMS, and place or end calls through scoped, approval-aware tools.
What it is
RevDesk Product MCP is the native agent interface for a focused set of calling, messaging, phone-number, caller-ID, and usage tools. Clients can initialize the server and inspect tool schemas without a credential. Reading organization data or invoking a tool requires a scoped RevDesk credential. Tool annotations distinguish read-only discovery from actions that can communicate externally, incur cost, or change configuration.
When to use RevDesk MCP server
- Let an MCP-compatible assistant discover and call supported RevDesk tools without generating a REST client.
- Give an agent a small, permissioned tool surface with machine-readable safety annotations.
- Inspect RevDesk usage or phone resources conversationally while keeping organization access scoped.
Recommended workflow
- 1Connect the client to the Streamable HTTP endpoint and initialize the server.
- 2Inspect tool schemas and annotations, then issue a key containing only the scopes the chosen tools require.
- 3Require confirmation for messages, calls, purchases, hangups, or other destructive and externally visible operations.
Safety and approval boundaries
- Tool discovery is public; organization data and tool execution are not.
- The MCP server is not an unrestricted replacement for the full v1 API.
- Credentials belong in the MCP host's secret store and must never be copied into prompts or source files.