How to Install the Didit MCP Server in Claude (Desktop and Code)

The Didit MCP (Model Context Protocol) server lets Claude run real identity and fraud checks for you — creating KYC (Know Your Customer) sessions, screening wallets, querying AML (Anti-Money Laundering) lists, and reading verification results — without you writing a single line of glue code. This guide walks through connecting it to both Claude Desktop (and Claude on the web) using a custom connector, and to Claude Code using one terminal command. The whole setup takes about five minutes, uses "Log in with Didit" OAuth (Open Authorization), and requires no API key in your config.

Key takeaways

• The Didit MCP server exposes 130+ tools across 11 categories — KYC and KYB (Know Your Business) sessions, standalone verification, workflows, transaction monitoring, AML screening, wallet screening, lists, cases, reports, webhooks, and billing.
• The hosted server lives at https://mcp.didit.me/mcp over Streamable HTTP — recommended over self-hosting for most teams.
• Authentication is OAuth 2.1 + PKCE ("Log in with Didit"). There is no API key to paste; you log in through business.didit.me and access is scoped to your console role.
• Claude Code installs with one command; Claude Desktop and Claude web install through Settings → Connectors → Add custom connector.
• New accounts get 500 free verifications per month with no card, and the MCP layer itself is free.

Option A: Install in Claude Code

Claude Code is the fastest path because it registers the server from your terminal.

Step 1 — Add the Didit server

Run this command in any project directory:

claude mcp add --transport http didit https://mcp.didit.me/mcp

This registers a server named didit using the Streamable HTTP transport pointed at the hosted endpoint. Notice there is no token or secret in the command — authentication happens interactively.

Step 2 — Log in with OAuth

Inside Claude Code, run:

/mcp

Select didit, then choose to authenticate. Claude Code opens your browser to business.didit.me, where you approve access with your existing Didit login. Once you confirm, the browser hands the session back and the didit server shows as connected. Because this uses OAuth 2.1 with PKCE, the tools you can call respect your console role — no long-lived key is stored on disk.

Step 3 — Confirm the tools loaded

Run /mcp again and open the didit server. You should see the tool catalog populated across the 11 categories. If tools are listed, you are ready.

Option B: Install in Claude Desktop (and Claude web)

Claude Desktop and Claude on the web both support custom connectors, which is how you add the Didit MCP server there.

Step 1 — Open Connectors settings

In Claude Desktop or Claude web, go to Settings → Connectors → Add custom connector.

Step 2 — Enter the Didit connector details

Fill in the two fields:

• Name: Didit
• URL: https://mcp.didit.me/mcp

Then click Connect.

Step 3 — Authorize in the browser

Claude opens a browser tab for "Log in with Didit." Approve access with your Didit account. When the tab closes, the Didit connector appears in your connector list as connected. As with Claude Code, there is no API key — the OAuth flow is the only credential, and it stays scoped to your user.

Step 4 — Enable the connector in a chat

Start a new conversation, open the tools or connectors menu, and make sure Didit is toggled on so Claude is allowed to call its tools.

Verify it works

The quickest sanity check is a read-only prompt that touches your account. In any Claude conversation with the connector enabled, ask:

List my organizations and applications.

Claude will call the appropriate Didit tool through the MCP server and return your organizations and their applications. If you see your real workspace data come back, the connection is live and authenticated correctly. From there you can move on to higher-intent prompts like:

Create a KYC verification session for a new user and give me the verification link.

Screen this wallet address for risk and summarize the findings.

Claude picks the right tool from the catalog, runs it against Didit, and reports the result in-line.

Troubleshooting

• The didit server shows as "needs auth" or disconnected. Re-run /mcp in Claude Code (or reopen Connectors settings in Desktop) and complete the browser login again. OAuth sessions can expire; re-authenticating restores access.
• No browser window opened during login. Make sure a default browser is set and pop-ups are allowed for the login step. In Claude Code, you can copy the printed authorization URL into a browser manually.
• "Add custom connector" is missing in Claude Desktop. Update to the latest Claude Desktop version — custom connector support ships in current releases. On Claude web, confirm your plan allows connectors.
• Tools do not appear after connecting. Toggle the Didit connector off and on in the conversation's tools menu, then start a fresh chat so Claude reloads the catalog.

Reference and next steps

• Read the Didit MCP overview and the installation guide for the full tool reference.
• See the developer landing page at didit.me/developers/mcp.
• Browse 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 make your first Claude-driven verification in minutes.