https://mcp.revdesk.com/mcp
Discovery: https://mcp.revdesk.com/.well-known/mcp
Official registry:
io.github.cell-labs-inc/revdesk-product
Agents may initialize the server and inspect tool names and schemas without a credential. Reading
organization data or invoking any tool requires a valid OAuth access token or API key;
unauthenticated tool calls fail before reaching the RevDesk API.
Connect
OAuth-capable MCP clients discover RevDesk’s authorization server automatically. Connect RevDesk, select the organization, review the named scopes, and approve the grant. If a client does not support OAuth, create an API key in Settings → API Keys, grant only the scopes the agent needs, then configure anAuthorization: Bearer rv_… header:
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.
Every tool publishes MCP safety annotations for read-only, destructive, idempotent, and open-world
behavior.
get_usage also advertises a ui:// resource using the MCP Apps media type so compatible
hosts can present a compact RevDesk usage surface beside the tool result.
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 OAuth grant or 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 and OAuth authorization server.