Skip to main content
RevDesk’s remote Model Context Protocol server gives AI agents a small, auditable tool surface for calling, SMS, phone numbers, caller IDs, and usage. It uses Streamable HTTP and the same organization-scoped API keys and least-privilege scopes as the REST API. Server URL: https://mcp.revdesk.com/mcp Discovery: https://mcp.revdesk.com/.well-known/mcp

​
Connect

Create an API key in Settings → API Keys, grant only the scopes the agent needs, then configure your MCP client with the server URL and an Authorization: Bearer rv_… header.
Keep API keys in your MCP client’s secret or environment-variable store. Never paste a key into a prompt, source file, or configuration file that will be committed.

​
Tools

The MCP layer calls the same v1 endpoints as the official TypeScript SDK. Scope checks, rate limits, idempotency, and tenant isolation are therefore enforced consistently.

​
Security and approvals

Tools that send messages, place calls, buy numbers, or hang up calls change external state or incur cost. Your agent host should require user approval before invoking them. For read-only discovery, use a separate key containing only the necessary :read scopes. The protected-resource metadata at https://mcp.revdesk.com/.well-known/oauth-protected-resource lists every supported scope and the accepted bearer method.