Install the Didit MCP

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 and approve the permissions.

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.

Hosted server (recommended)

Add the server with the CLI, then trigger the sign-in:

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.

Settings → Connectors → Add custom connector.
Name it Didit and set the URL to:

https://mcp.didit.me/mcp

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

The Didit tools then appear in the chat’s tool menu.

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):

{
  "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.

With GitHub Copilot agent mode, add .vscode/mcp.json:

{
  "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.

Windsurf connects through the mcp-remote bridge. Add to ~/.codeium/windsurf/mcp_config.json:

{
  "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.

Add a context server in Zed’s settings.json:

{
  "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.

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.

Self-hosting

Want to run the server yourself (it’s open source, MIT — @didit-protocol/mcp-server)? You can 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.

Hosted server (recommended)

Self-hosting

Next steps

Authentication

Tools reference

​Hosted server (recommended)

​Self-hosting

​Next steps

Authentication

Tools reference

Hosted server (recommended)

Self-hosting

Next steps