Install the Didit MCP: Claude, Cursor, VS Code, Windsurf

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.

Using Claude? The Connect Claude page has the one-click connector link that opens the Add custom connector dialog with the name and URL pre-filled, so you only have to confirm and sign in.

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.

Web: click Add Didit to Claude → and confirm the pre-filled dialog.Desktop: 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 registers itself with Didit through Dynamic Client Registration and 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. Point VS Code at the full /mcp URL: the server publishes its OAuth resource metadata for that path.

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.

Any client that implements MCP over Streamable HTTP with OAuth 2.1 can connect to https://mcp.didit.me/mcp directly. It discovers the authorization server from https://mcp.didit.me/.well-known/oauth-protected-resource/mcp, registers itself with Dynamic Client Registration and runs the PKCE flow. The server only accepts POST on /mcp; GET and DELETE answer 405, because it is stateless and keeps no server-initiated stream.A client that only speaks stdio can use the same mcp-remote bridge as Windsurf and Zed:

npx -y mcp-remote@latest https://mcp.didit.me/mcp

To try the server without a client, the MCP Inspector connects to the same URL and walks you through the sign-in.

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.

The hosted server answers GET https://mcp.didit.me/healthz with its version.

Verify your connection

After you sign in, ask your client:

Use the Didit MCP server to call didit_context_get and list my organizations and applications.

The agent should call didit_context_get and show your organizations with their applications. If it says it has no Didit tools, the server did not connect or sign-in did not finish: see Troubleshooting.

Self-hosting

The hosted server is built from the open-source repository github.com/didit-protocol/mcp (MIT). Every release is also published to npm as @didit-protocol/mcp-server, so you can run the stdio server straight from npm or build either entry point from a clone. One codebase ships two entry points:

Entry point	Mode	Transport	Authentication
`dist/http.js`	Hosted	Streamable HTTP on `MCP_PORT` (default 3000), `POST /mcp`, `GET /healthz`	OAuth 2.1 Bearer, validated by token introspection
`dist/index.js`	stdio (headless)	MCP stdio	A user access token in `DIDIT_ACCESS_TOKEN`

Both modes act as a Didit user. There is no application API-key mode.

Clone and build

git clone https://github.com/didit-protocol/mcp.git && cd mcp
npm install && npm run build

Or build the container: docker build -t didit-mcp .. The image runs dist/http.js as a non-root user, exposes port 3000 and has a health check on /healthz.

Run the HTTP server (OAuth)

Copy .env.example to .env and fill in the hosted-mode values, then:

node dist/http.js
# or
docker run -p 3000:3000 --env-file .env didit-mcp

The server is an OAuth resource server only. It needs MCP_RESOURCE_URI set to the full public URL of the transport (for example https://mcp.example.com/mcp, not the bare origin) and the credentials it uses to introspect tokens (MCP_OAUTH_CLIENT_ID, MCP_OAUTH_CLIENT_SECRET) against the Didit authorization server. The full variable list is in Advanced → self-hosting.

Or run it over stdio (headless)

For a local agent that cannot run an OAuth flow, run the published package (no clone needed) and pass a user access token in the environment:

DIDIT_ACCESS_TOKEN=<user-access-token> npx -y @didit-protocol/mcp-server

From a clone, DIDIT_ACCESS_TOKEN=<user-access-token> node dist/index.js does the same. Without a token, the agent can sign in with didit_account_login, followed by didit_account_verify_2fa when the account has two-factor authentication.Optional MCP_DEFAULT_ORG and MCP_DEFAULT_APP pin the scope for single-tenant setups. Register it in Claude Code with:

claude mcp add didit-local -e DIDIT_ACCESS_TOKEN=<user-access-token> -- npx -y @didit-protocol/mcp-server

Or in Cursor’s mcp.json:

{
  "mcpServers": {
    "didit-local": {
      "command": "npx",
      "args": ["-y", "@didit-protocol/mcp-server"],
      "env": { "DIDIT_ACCESS_TOKEN": "<user-access-token>" }
    }
  }
}

The open-source stdio server does not include the hosted server’s Travel Rule, marketplace, fraud network and transaction SDK token tools, or its compliance tools other than building a workflow. It adds didit_org_top_up, didit_org_reveal_application_api_key, and five account-setup tools (didit_account_register, didit_account_verify_email, didit_account_resend_otp, didit_account_login, didit_account_verify_2fa) that take credentials as arguments and therefore never ship on a remote connector. File-taking tools also accept *_path arguments on stdio, since the server shares your filesystem.

Guides

Authentication

Model Context Protocol (MCP)

Web SDKs

Native SDKs

Server SDKs

Integrations

Install the Didit MCP: Claude, Cursor, VS Code, Windsurf

Hosted server (recommended)

Verify your connection

Self-hosting

Next steps

Authentication

Tools reference

​Hosted server (recommended)

​Verify your connection

​Self-hosting

​Next steps

Authentication

Tools reference

Hosted server (recommended)

Verify your connection

Self-hosting

Next steps