> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zudo.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Remote MCP

> Connect AI apps to Zudo through the remote MCP server with OAuth.

Zudo exposes a remote MCP server so AI apps can use the same machine-facing capabilities as the Zudo API.

## Connection details

* **Server URL:** `https://zudo.so/mcp`
* **Auth:** OAuth with authorization code + PKCE
* **Recommended scopes:** `mcp api`

<Note>If you self-host Zudo or use a staging environment, replace `https://zudo.so` with your own origin.</Note>

## What the MCP server can do

The MCP tool set mirrors Zudo's external API, including operations for:

* accounts
* contacts
* conversations
* issues
* meetings
* requests
* tasks

As the external API grows, the MCP tool set grows with it.

## How authentication works

<Steps>
  <Step title="Add the MCP server in your AI app">Enter the Zudo MCP server URL: `https://zudo.so/mcp`.</Step>

  <Step title="Sign in to Zudo">
    If you are not already signed in, Zudo redirects you to the normal sign-in flow and then returns you to the OAuth
    approval page.
  </Step>

  <Step title="Approve access">
    Zudo shows a consent screen listing the client name, redirect URI, and requested scopes.
  </Step>

  <Step title="Let the client store the tokens">
    The AI app receives an OAuth access token and refresh token. You usually do not need to copy or manage these
    manually.
  </Step>
</Steps>

## Organization scoping

Your MCP connection is bound to the same organization scope as the API key record behind the OAuth grant.

<Warning>
  If you belong to multiple organizations, switch to the correct organization in Zudo before approving the connection.
</Warning>

## When to use API keys instead

Use an API key when you are building direct REST API integrations or running backend jobs against `/api/v1`.

Use MCP when you want an AI client to discover tools and call Zudo through the MCP protocol.

## Advanced connection info

Most clients can discover everything automatically from the MCP server URL. If a client asks for explicit OAuth metadata, use:

* **Authorization server metadata:** `https://zudo.so/.well-known/oauth-authorization-server`
* **Protected resource metadata:** `https://zudo.so/.well-known/oauth-protected-resource/mcp`
* **Authorization endpoint:** `https://zudo.so/authorize`
* **Token endpoint:** `https://zudo.so/token`

## Troubleshooting

* If the client connects but tool calls fail, make sure the granted scopes include `api` as well as `mcp`.
* If you hit a sign-in loop, sign out of Zudo in your browser and restart the connection flow.
* If data appears to come from the wrong workspace, switch organizations in Zudo and reconnect.
* If your client supports removing or resetting a connector, disconnect and reconnect to force a fresh OAuth grant.

## App-specific guides

* [Connect Claude](/integrations/claude)
* [Connect ChatGPT](/integrations/chatgpt)