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

# Install the Didit MCP

> Connect the Didit MCP server to Claude, Cursor, VS Code, Windsurf, Zed, or any MCP client. One URL, Log in with Didit (OAuth) — no API keys.

Pick your client below. The **hosted** server (`https://mcp.didit.me/mcp`) needs no API key — on first connect your client opens a browser and you **[Log in with Didit](/integration/mcp/authentication)** and approve the permissions.

<Note>
  Clients that don't yet speak remote/HTTP MCP (Windsurf, Zed) connect through the `mcp-remote` bridge, which forwards stdio to the hosted URL and handles the OAuth handshake for you.
</Note>

***

## Hosted server (recommended)

<Tabs>
  <Tab title="Claude Code">
    Add the server with the CLI, then trigger the sign-in:

    ```bash theme={null}
    claude mcp add --transport http didit https://mcp.didit.me/mcp
    ```

    Start Claude Code and run `/mcp` — it opens the browser for **Log in with Didit**. After you approve, the `didit` tools are available.
  </Tab>

  <Tab title="Claude Desktop">
    1. **Settings → Connectors → Add custom connector**.
    2. Name it `Didit` and set the URL to:

    ```text theme={null}
    https://mcp.didit.me/mcp
    ```

    3. Click **Connect** and complete **Log in with Didit** in the browser.

    The Didit tools then appear in the chat's tool menu.
  </Tab>

  <Tab title="Cursor">
    Add to `~/.cursor/mcp.json` (global) or `.cursor/mcp.json` (per-project):

    ```json theme={null}
    {
      "mcpServers": {
        "didit": {
          "url": "https://mcp.didit.me/mcp"
        }
      }
    }
    ```

    Or use **Settings → Tools & Integrations → New MCP Server**. Cursor opens the browser for sign-in on first use.
  </Tab>

  <Tab title="VS Code">
    With GitHub Copilot agent mode, add `.vscode/mcp.json`:

    ```json theme={null}
    {
      "servers": {
        "didit": {
          "type": "http",
          "url": "https://mcp.didit.me/mcp"
        }
      }
    }
    ```

    Or run **MCP: Add Server** from the command palette and choose **HTTP**. Sign in when prompted.
  </Tab>

  <Tab title="Windsurf">
    Windsurf connects through the `mcp-remote` bridge. Add to `~/.codeium/windsurf/mcp_config.json`:

    ```json theme={null}
    {
      "mcpServers": {
        "didit": {
          "command": "npx",
          "args": ["-y", "mcp-remote@latest", "https://mcp.didit.me/mcp"]
        }
      }
    }
    ```

    Open **Settings → Cascade → MCP Servers → Manage** to confirm it loaded, then sign in via the browser.
  </Tab>

  <Tab title="Zed">
    Add a context server in Zed's `settings.json`:

    ```json theme={null}
    {
      "context_servers": {
        "didit": {
          "source": "custom",
          "command": "npx",
          "args": ["-y", "mcp-remote@latest", "https://mcp.didit.me/mcp"]
        }
      }
    }
    ```

    Zed launches the bridge and opens the browser for **Log in with Didit**.
  </Tab>
</Tabs>

<Info>
  **No API key in the config.** The hosted server authenticates you in the browser and acts as **you** — every organization you belong to, with your role's permissions. See [Authentication](/integration/mcp/authentication).
</Info>

***

## Self-hosting

Want to run the server yourself? It's open source (MIT) — [github.com/didit-protocol/mcp](https://github.com/didit-protocol/mcp). Clone the repo and run it with Docker or Node — host the HTTP/OAuth server or run it over stdio for headless use. It still authenticates as a Didit **user** — there's no API-key mode. See [Advanced → self-hosting](/integration/mcp/advanced#self-hosting).

***

## Next steps

<CardGroup cols={2}>
  <Card title="Authentication" icon="lock" href="/integration/mcp/authentication">
    Sign-in, scopes, and roles.
  </Card>

  <Card title="Tools reference" icon="wrench" href="/integration/mcp/tools">
    Everything the agent can call.
  </Card>
</CardGroup>