Add Didit to Claude
Opens claude.ai with the Add custom connector dialog pre-filled: name Didit, URL mcp.didit.me/mcp. Confirm, sign in with Didit, done.
Set up by surface
- Claude web
- Claude Desktop
- Claude Code
- Click Add Didit to Claude →. The Add custom connector dialog opens with every field filled in.
- Confirm the dialog.
- Complete Log in with Didit in the browser and approve the permissions.
Didit, URL https://mcp.didit.me/mcp.No API key anywhere. The hosted server uses OAuth 2.1 with PKCE and acts as you: every organization you belong to, with your role’s permissions, under the
didit:management and didit:verification scopes. See Authentication.What Claude can do once connected
The hosted server exposes 115 tools across sessions, workflows, transactions, cases, analytics, and more. Prompts that work on day one:- “Create a KYC workflow with ID verification, passive liveness, and AML screening, then give me a verification link.”
- “Show me the sessions waiting in my review queue and summarize the warnings on each.”
- “Write a transaction monitoring rule that flags more than 3 transfers over $1,000 in an hour, and back-test it against the last 90 days.”
- “Which country generated the most declined sessions this month?”
Troubleshooting
- The dialog opens empty. You followed a link that lost its query string. Paste the full connector link from this page, or add the connector manually with URL
https://mcp.didit.me/mcp. - Sign-in loops or fails. Log in at business.didit.me first, then reconnect. The MCP server authenticates against the same account.
- Tools are missing. Your role in the organization limits which tools appear. An owner or admin sees all 115; narrower roles see fewer. See Authentication.
Next steps
Tools reference
Everything Claude can call, tool by tool.
Example prompts
Longer worked examples with real payloads.
Other clients
Cursor, VS Code, Windsurf, Zed, and self-hosting.
Authentication
OAuth flow, scopes, and roles.