How to Connect the Didit MCP Server to Cursor and VS Code

If you build in Cursor or VS Code, you can wire the Didit MCP (Model Context Protocol) server straight into your editor's AI assistant. Once connected, your assistant can create KYC (Know Your Customer) sessions, run KYB (Know Your Business) checks, screen wallets, query AML (Anti-Money Laundering) lists, and read verification results — all from the same window where you write code. This guide gives you the exact JSON config for both editors, the OAuth (Open Authorization) login flow, and how to verify the tools loaded. There is no API key to store in the config; authentication happens through "Log in with Didit."

Key takeaways

• The Didit MCP server exposes 130+ tools across 11 categories — KYC and KYB sessions, standalone verification, workflows, transaction monitoring, AML screening, wallet screening, lists, cases, reports, webhooks, and billing.
• The hosted endpoint is https://mcp.didit.me/mcp over Streamable HTTP — recommended over self-hosting for most teams.
• Both editors connect via a small JSON file: ~/.cursor/mcp.json for Cursor and .vscode/mcp.json for VS Code.
• Authentication is OAuth 2.1 + PKCE ("Log in with Didit") via business.didit.me — no API key in config, and access is scoped to your console role.
• New accounts get 500 free verifications per month with no card; the MCP layer is free.

Step 1 — Connect the Didit MCP server to Cursor

Cursor reads MCP servers from ~/.cursor/mcp.json in your home directory (you can also use a per-project .cursor/mcp.json).

Create or edit the file and add the didit server:

{
  "mcpServers": {
    "didit": {
      "url": "https://mcp.didit.me/mcp"
    }
  }
}

Save the file. Notice there is no token or secret — only the hosted URL. If you already have other MCP servers defined, add the didit entry alongside them inside mcpServers.

Now open Cursor Settings → MCP (or Tools/Integrations, depending on your version). The didit server appears in the list. Cursor prompts you to authenticate; approve it and complete the "Log in with Didit" flow in your browser at business.didit.me. Because this uses OAuth 2.1 with PKCE, no long-lived credential is written to disk and the tools you can call respect your console role.

Step 2 — Connect the Didit MCP server to VS Code

VS Code reads workspace MCP servers from .vscode/mcp.json at the root of your project. Create that file and add:

{
  "servers": {
    "didit": {
      "type": "http",
      "url": "https://mcp.didit.me/mcp"
    }
  }
}

Note the differences from Cursor: VS Code uses the key servers (not mcpServers) and requires an explicit "type": "http" for the Streamable HTTP transport. Save the file.

VS Code detects the new server and offers to Start it. Start the didit server; VS Code walks you through the "Log in with Didit" OAuth flow in your browser. Once you approve access at business.didit.me, the server is connected and its tools become available to Copilot Chat in agent mode.

Step 3 — A note on Windsurf and Zed

If you use Windsurf or Zed, those clients connect through a small bridge command instead of a plain URL. In the client's MCP configuration, run the Didit endpoint through mcp-remote:

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

Add that command to the client's MCP server config; the OAuth login flow works the same way.

Verify the tools loaded

After authenticating, confirm the catalog is present.

• In Cursor: open Settings → MCP and expand the didit server. You should see its tools listed across the 11 categories.
• In VS Code: open the MCP servers view (or run the "MCP: List Servers" command) and confirm didit shows as running with its tools available in agent mode.

Then run a read-only prompt in your assistant to confirm authentication end to end:

List my organizations and applications.

Your assistant calls the Didit tool through the MCP server and returns your organizations and their applications. If your real workspace data comes back, you are connected. From there, try higher-intent prompts:

Create a KYC verification session and give me the verification link.

Screen this wallet address for risk and summarize the result.

Your editor's assistant selects the right tool, calls Didit, and reports back — right next to your code.

Troubleshooting

• The server doesn't appear after editing the JSON. Check for a JSON syntax error (a stray trailing comma is the usual culprit), confirm the file path and key are correct — mcpServers for Cursor, servers for VS Code — then reload the editor.
• VS Code says the server won't start. Make sure you included "type": "http"; VS Code needs it to use the Streamable HTTP transport.
• OAuth login never completes. Allow browser pop-ups so the "Log in with Didit" window can open, and finish the approval at business.didit.me. Re-trigger auth from the MCP settings if the session expired.
• Tool calls return a permissions error. MCP access mirrors your Didit console role. Sign in with an account that has the required permissions.

Reference and next steps

• Read the Didit MCP overview and the installation guide for the complete tool reference.
• See the developer landing page at didit.me/developers/mcp.
• Inspect or self-host the open-source server (MIT licensed) at github.com/didit-protocol/mcp.

Didit is infrastructure for identity and fraud, trusted by 1,500+ companies, backed by $7.5M, a Y Combinator W26 company, profitable, and live across 220+ countries. Full KYC runs $0.33, wallet screening $0.15, and AML screening $0.20 — with 500 free verifications every month and no card required.

Start free at business.didit.me and put identity and fraud tools inside your editor today.