Skip to main content
This Didit Academy lesson connects the hosted MCP server to Claude over OAuth, then builds a KYC workflow from one prompt, queries the review queue, and back-tests transaction rules against 90 days of history. The Didit MCP server connects any Model Context Protocol client — Claude, Cursor, VS Code, Windsurf, Zed, and more — directly to the Didit identity platform. Once connected, an agent can run KYC, KYB, AML screening, transaction monitoring, and full workspace operations (workflows, sessions, lists, webhooks, billing) through natural-language commands.
The Didit MCP is read-and-write: agents can create sessions, configure workflows, update statuses and add entries to your lists on your behalf. Every client asks you to review tool calls before they run — keep that on, especially for write and delete actions.

​
Get started in 30 seconds

The fastest path is the hosted server — one URL, no API key. Your client opens a browser, you Log in with Didit, approve the permissions, and you’re connected.
Hosted endpoint
On Claude for web, Add Didit to Claude → pre-fills the connector dialog — confirm, sign in with Didit, done. Full walkthrough on Connect Claude. Source is on GitHub (MIT).

Install in your client

Copy-paste setup for Claude, Cursor, VS Code, Windsurf, and Zed.

How sign-in works

“Log in with Didit” (OAuth 2.1 with PKCE) — no API keys, no secrets in config.

Browse the tools

156 tools across sessions, workflows, standalone checks, transaction monitoring, lists, cases, reports and webhooks.

See it in action

Example prompts and end-to-end agent conversations.

​
How it works

The hosted MCP is an OAuth 2.1 resource server; the Didit Business Console (business.didit.me) is the authorization server. You connect with one URL, Log in with Didit in the browser, and the MCP then acts as you — across every organization you belong to, with your console role’s permissions.
The MCP acts as a Didit user, not an application — there is no API-key mode. Every tool calls the user-scoped console endpoints, which only accept your Bearer token. (To call the raw REST API with an application API key — e.g. creating sessions from your own backend — use the REST API directly; that’s separate from this MCP.)
The server is stateless Streamable HTTP: one POST https://mcp.didit.me/mcp per request, no session affinity, and a public health check at GET https://mcp.didit.me/healthz. Prefer to run the server yourself? You can — see Installation → self-hosting. It still authenticates the user via OAuth (or a user Bearer token for headless stdio runs). The tools return the verbatim JSON of the underlying Didit endpoints. See Authentication for the full picture.

​
What can you do with it?

Ask in plain language. A few things the agent can do across all of your apps at once:
  • “Show me the last 5 in-review sessions across all my apps.”
  • “How many people tried phone verification but dropped off in the last 15 days?”
  • “Create a KYC workflow with an ID scan and liveness, then give me a verification link.”
  • “Find the customer with vendor_data user_8842 — which app are they in and what’s their status?”
  • “Screen this wallet for AML risk and add it to the blocklist if it hits.”
  • “Register a webhook destination for status updates on my endpoint.”
  • “What’s my credit balance and conversion rate this month?”

​
Built for the agentic era

Most verification platforms require manual console setup. Didit lets an agent do the whole thing — configure workflows, create and review sessions, wire webhooks, and monitor billing — end to end. Pair the MCP with the one-prompt integration and an agent can ship a complete integration (backend route + frontend SDK + webhook handler) while calling MCP tools to create the workflow and session live.

Installation

Per-client setup for Claude, Cursor, VS Code, Windsurf, Zed, plus self-hosting.

Authentication

OAuth sign-in, scopes, and roles.

Tools reference

Every tool, grouped by area, with its scope and role permission.

Advanced & troubleshooting

Roles, cross-app behavior, branching workflows, webhooks, self-hosting.