Skip to main content
RevDesk’s remote Model Context Protocol server lets an AI client set up and run a workspace: lines and caller ID, agents, texting settings, contacts, conversations, calls, bookings, tasks and usage. It uses Streamable HTTP. Every tool calls the same v1 endpoints as the TypeScript SDK, so scopes, rate limits, idempotency and tenant isolation work exactly as they do for the REST API. Setting it up in ChatGPT or Claude without code? See Use RevDesk in ChatGPT or Claude. Any client can initialize the server and list tools without a credential. Reading workspace data or calling a tool needs an OAuth access token or an API key. Unauthenticated tool calls fail before they reach the API.

Connect with OAuth

OAuth clients need only the server URL. The client finds RevDesk’s authorization server from the protected resource metadata and registers itself automatically, so there’s no client ID to copy. The person signs in to RevDesk, picks a workspace, reviews the scopes and approves. The protected resource metadata lists every supported scope.

Connect with an API key

For clients without OAuth, create a key in Settings › API Keys with only the scopes the agent needs, and send it as a bearer header:
Keep the key in your client’s secret or environment store. Never paste it into a prompt or a file you commit.

Tools

whoami shows which workspace and scopes the connection has. Tools only a workspace admin can use are not listed for other members, and results leave out fields that are empty. Tools marked Confirm contact a customer, spend money, or remove something; their descriptions tell the model to ask the user first.

Account

Workspaces

These manage child workspaces under the connection’s workspace, like an agency’s dealers or a group’s stores. See Sub-entities. To set up or run one of those workspaces, pass its id as workspace_id on any other tool. The signed-in person must be a member of that workspace, and their role there applies. Over the REST API, send the RevDesk-Workspace header instead.

Lines and trust

Configure

Team and routing

Lead sources, apps and inventory

Agents and knowledge

Calendars, hours and settings

Campaigns and reports

Everyday work

Report

get_usage also offers a ui:// resource with the MCP Apps media type, so hosts that support it can show a compact usage card beside the result. Connecting a calendar, CRM or other app needs a sign-in on that app’s site, so those tools return a connect_url to the right RevDesk settings page. Inventory feeds are set up by RevDesk.

Safety

Every tool publishes MCP annotations for read-only, destructive, idempotent and open-world behavior. The server tells the model to describe exactly what will happen and get the user’s confirmation before anything that spends money, contacts a customer, or is marked destructive. For read-only use, grant only :read scopes.