> ## Documentation Index
> Fetch the complete documentation index at: https://docs.didit.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Didit MCP Server

> Connect Claude, Cursor, VS Code, Windsurf, and any MCP client to Didit identity verification. Agent-native KYC, KYB, and AML over natural language — hosted (Log in with Didit) or self-hosted.

The **Didit MCP server** connects any [Model Context Protocol](https://modelcontextprotocol.io) 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.

<Note>
  The Didit MCP is **read-and-write**: agents can create sessions, configure workflows, update statuses, and move credits on your behalf. Every client asks you to review tool calls before they run — keep that on, especially for write and delete actions.
</Note>

***

## 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.

```text Hosted endpoint theme={null}
https://mcp.didit.me/mcp
```

<CardGroup cols={2}>
  <Card title="Install in your client" icon="download" href="/integration/mcp/installation">
    Copy-paste setup for Claude, Cursor, VS Code, Windsurf, and Zed.
  </Card>

  <Card title="How sign-in works" icon="key" href="/integration/mcp/authentication">
    "Log in with Didit" (OAuth 2.1) — no API keys, no secrets in config.
  </Card>

  <Card title="Browse the tools" icon="wrench" href="/integration/mcp/tools">
    130+ tools across sessions, workflows, AML, Travel Rule, marketplace, lists, webhooks, and billing.
  </Card>

  <Card title="See it in action" icon="comments" href="/integration/mcp/examples">
    Example prompts and end-to-end agent conversations.
  </Card>
</CardGroup>

***

## How it works

The hosted MCP is an OAuth 2.1 **resource server**; the Didit console 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.

<Note>
  **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](/openapi-25.json) directly; that's separate from this MCP.)
</Note>

Prefer to run the server yourself? You can — see [Advanced → self-hosting](/integration/mcp/advanced#self-hosting). It still authenticates the user via OAuth (or a user Bearer for headless runs).

The tools return the verbatim JSON of the underlying Didit endpoints. See [Authentication](/integration/mcp/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?"*
* *"Add this wallet to the blocklist and screen it for AML."*
* *"Register a webhook for status updates and show me the signing secret."*
* *"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 — **self-register** an account (no browser, no 2FA on programmatic accounts), **configure workflows**, **create and review sessions**, **wire webhooks**, and **monitor billing** — end to end. Pair the MCP with the [one-prompt integration](/integration/integration-prompt) 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.

<CardGroup cols={2}>
  <Card title="Installation" icon="download" href="/integration/mcp/installation">
    Per-client setup for Claude, Cursor, VS Code, Windsurf, Zed.
  </Card>

  <Card title="Authentication" icon="lock" href="/integration/mcp/authentication">
    OAuth sign-in, scopes, and roles.
  </Card>

  <Card title="Tools reference" icon="wrench" href="/integration/mcp/tools">
    Every tool, grouped by area.
  </Card>

  <Card title="Advanced & troubleshooting" icon="gear" href="/integration/mcp/advanced">
    Scopes, cross-app behavior, webhooks, self-hosting.
  </Card>
</CardGroup>