How to connect Didit to Claude

Connect Claude Web, Desktop and Cowork to Didit MCP. Review pending didit kyc verification sessions, check aml risk flags for users, and more using natural language, with authentication handled for you.

Didit logoDidit
Api Key

Didit is an identity verification and compliance API platform for KYC, KYB, AML, and fraud prevention. It helps teams onboard users faster while reducing risk and meeting compliance needs.

10 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Didit account to Claude via Composio Connect, enabling it to review pending Didit KYC verification sessions, check AML risk flags for users, create identity verification for new customer, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Didit with

Connecting Didit to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Didit account

Back in Claude, ask it to connect to Didit or give it any Didit-related task.

For example, ask Claude to:

  • "Review pending Didit KYC verification sessions"
  • "Check AML risk flags for users"
  • "Create identity verification for new customer"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Didit account is ready to use.

What is the Didit Claude Connector, and what's possible with it?

The Didit MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Didit account. It provides structured and secure access so your agent can perform Didit operations on your behalf.

Troubleshooting

1. Why does Claude not use the Composio connector for Didit?

The connector can show as connected, but Claude must use it in each Didit conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Didit again.

2. Why does Claude show an MCP server error before Didit connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Didit.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Didit.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Didit authorization link not work?

The Composio connector is one server. Your Didit account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Didit connection.
  • Composio creates a fresh Didit authorization link.
  • Open that link in your browser and finish the Didit sign-in.

4. Why do Didit actions fail after they worked before?

The Didit connection can expire or lose permission.

  • Ask Claude to inspect the Didit connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Didit account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Didit.
  • If the action still fails with a permission error, check that the connected account has that permission in Didit itself.

5. How do I switch to a different Didit account?

Claude can manage the Didit connection for you.

  • Ask Claude to disconnect or delete the current Didit account.
  • Ask Claude to connect Didit again.
  • Open the new Composio authorization link for Didit.
  • Sign in with the other Didit account in the browser.
  • After the account connects, ask Claude to retry the Didit task.

6. Why is my Didit connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Didit connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Didit tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Didit.
TOOLS

Supported Tools

Every Didit action and event your agent gets out of the box.

Create Verification Session

Create a hosted KYC or KYB verification session from a published workflow and return the URL to give the end user.

Get Billing Balance

Read the organization's prepaid Didit credit balance and auto-refill settings before starting billable verification work.

Get Business

Fetch one aggregated KYB business profile by its exact vendor_data identifier.

Get User

Fetch one aggregated KYC user profile by its exact vendor_data identifier.

Get Verification Decision

Retrieve the complete current KYC or KYB decision and all feature reports for one verification session.

Get Workflow

Fetch the full configuration and pricing of one workflow version.

List Businesses

List business profiles aggregated from KYB sessions, including status, session counts, registry identifiers, and verification summaries.

List Users

List user profiles aggregated from KYC sessions, including status, session counts, and feature summaries.

List Verification Sessions

List and filter KYC, KYB, or standalone verification sessions.

List Workflows

List configured verification workflow versions, their publication status, feature summary, and expected per-run pricing.

FAQ

Frequently asked questions

With a standalone Didit MCP server, the agents and LLMs can only access a fixed set of Didit tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Didit and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Didit tools.

Yes, absolutely. You can configure which Didit scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Didit data and credentials are handled as safely as possible.

Start with Didit.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Didit tool your agent needs.Free to start.

Start building