Skip to main content
Claude connects to the hosted Didit MCP server with one link. Click it, confirm the pre-filled dialog, and sign in with your Didit account. There is no API key to copy and nothing to install.

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.
The full connector link, if you want to share it or put it behind your own button:
This is the same link the Business Console shows on its integrate page. In the MCP Academy lesson, the 1:42 chapter shows this exact flow: adding the connector in Claude, the OAuth sign-in, and the tools appearing in the chat.

Set up by surface

  1. Click Add Didit to Claude →. The Add custom connector dialog opens with every field filled in.
  2. Confirm the dialog.
  3. Complete Log in with Didit in the browser and approve the permissions.
The Didit tools then show up in the chat’s tool menu, split into read-only, write and destructive groups. If you prefer the manual path: Settings → Connectors → Add custom connector, name 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

A signed-in user sees 189 tools across sessions, workflows, standalone checks, transaction monitoring, 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?”
The MCP Academy lesson runs each of these against a live account.

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.
  • A tool answers with missing_scope. Your role in that organization lacks the permission the tool needs; the error names it. Ask an owner or admin to grant it. See Authentication.
  • Using another client? See Connect ChatGPT, Connect Cursor, Connect VS Code or Connect Codex.
  • You cannot find didit_org_top_up or didit_org_reveal_application_api_key. Both are hidden from the hosted connector on purpose, so it never moves money: it gives you a console link to top up, and you read API keys in the console. To let an agent top up with your saved card, turn on “Connected AI agents can top up with your saved card” in the console and see Agent top-ups.

Next steps

Tools reference

Everything Claude can call, tool by tool.

Example prompts

Longer worked examples with real payloads.

Other clients

ChatGPT, Cursor, VS Code, Codex, Windsurf, Zed and self-hosting.

Authentication

OAuth flow, scopes, and roles.
Last modified on November 12, 2026