ComplyCube MCP connector
The ComplyCube connector brings identity verification clients, addresses, documents and live photos into Claude, ChatGPT, Cursor and any MCP client, so your team can check, update and clean up verification records under their own ComplyCube access.
- Connects with an API key
- Free 14-day trial
- No credit card
Show ComplyCube clients with a high risk profile
Working in ComplyCube with Elaichi
-
Get single ComplyCube client by ID
-
List all ComplyCube clients
-
ComplyCube clients get risk profile
How to connect ComplyCube to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
ComplyCube MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
ComplyCube MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
ComplyCube MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
ComplyCube MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
ComplyCube MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect ComplyCube to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with ComplyCube through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in ComplyCube is logged.
-
Compliance
Check a client's risk profile before approval
Pull up a ComplyCube client, read their risk profile and see which documents and live photos are attached, all in one ask before signing off on onboarding.
-
Onboarding
Create the client record from a signup
When a new applicant comes in, create the ComplyCube client, add their address and attach the ID document they sent, without switching between screens.
-
Support
Fix a mistyped name or address
A customer says their date of birth or address is wrong on file. Find the ComplyCube client, correct the record or the address and confirm the change back to them.
-
Risk
Review pending verifications across clients
List ComplyCube clients and their documents to spot anyone still waiting on a passport upload or a live photo, then chase the right people.
-
Legal
Redact documents after a retention deadline
Redact ComplyCube documents and live photos for clients past your retention period, and remove the record entirely when a deletion request comes in.
-
Operations
Retrieve a document image for an audit
An auditor asks for proof of a specific verification. Download the ComplyCube document image or live photo for that client and hand it over.
Try asking
- “Show ComplyCube clients with a high risk profile”
- “List documents added to ComplyCube clients this week”
- “Which ComplyCube clients have no verified address yet?”
What connecting ComplyCube gets you
6 screens from Elaichi, each doing one job for your ComplyCube account.
Ask Elaichi to work across your apps.
Show ComplyCube clients with a high risk profile
List documents added to ComplyCube clients this week
Which ComplyCube clients have no verified address yet?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about ComplyCube clients in plain language.
Answers come from live ComplyCube clients, documents and risk profiles.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach ComplyCube.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
All 63 ComplyCube tools are ready here.
Clients, addresses, documents and risk profiles, with no custom code to write.
Toolboxes
Each team gets its own ComplyCube toolbox.
Compliance, Onboarding and Risk each see the ComplyCube tools their work needs.
Shared connections
Share a ComplyCube account, never the key.
Teammates screen clients and documents through a connection without seeing a credential.
Audit log
Every ComplyCube call is written down.
When, who, what happened, type and resource, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
ComplyCube digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch clients
ComplyCube
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
ComplyCube
Queued
Automations
A schedule runs your ComplyCube review.
Fetch clients, group them, draft a digest, approve it, post back to ComplyCube.
ComplyCube health
Refreshed 4 minutes ago · every 15 minutes · from the clients collection
Clients
1,284 ↓ 12%
Addresses
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Clients created
Last 14 days
By team
Share of activity
Compliance EMEA 34%
Onboarding 27%
Risk Review 21%
Support 18%
Collections and dashboards
ComplyCube health, counted on a schedule.
Four metrics, 14 days of clients created, and a breakdown by team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for ComplyCube
All three can connect ComplyCube to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over ComplyCube tools | Allow or restrict single ComplyCube tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per ComplyCube call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
ComplyCube tools for your AI agents
63 tools are ready to call through Elaichi's MCP endpoint the moment you connect ComplyCube, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect ComplyCube to Claude?
Connect ComplyCube in Elaichi by pasting a ComplyCube API key when asked, then in Claude go to Customize, then Connectors, then Add and paste https://api.elaichi.ai/mcp. There is no OAuth application to register in ComplyCube and no client ID or secret to generate. Sign in to Elaichi from Claude and ComplyCube is ready to use.
Does ComplyCube work with ChatGPT and Cursor as well as Claude?
Yes. Once ComplyCube is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect ComplyCube once and every client picks it up.
What can an AI agent actually do with my ComplyCube data?
With ComplyCube connected, an agent can look up a client and their risk profile, create or update clients and addresses, attach ID documents and upload or download their images, retrieve live photos, and redact or delete documents and photos when a record must be cleaned up. Because ComplyCube has many actions, short concrete asks such as "show the documents for client Ana Ruiz" work better than long sentences.
Does connecting ComplyCube give the AI everything in my account?
No. Every call to ComplyCube runs under the access of the person who signed in, so the agent sees the clients, documents and live photos that person's ComplyCube key allows and nothing more. Elaichi can narrow that further by restricting actions, and it can never widen it beyond what ComplyCube already grants.
Can I stop an agent from deleting or changing things in ComplyCube?
Yes. Restrictions in Elaichi work per action, so you can allow reading ComplyCube clients and documents while restricting deletion, redaction or updates. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
What happens to a ComplyCube connection when someone leaves?
Offboarding a person in Elaichi ends their access to ComplyCube at once, across every client they used. A shared ComplyCube connection keeps working for everyone else on the team. If you disconnect ComplyCube in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.
Does the ComplyCube MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. ComplyCube is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for ComplyCube?
Yes. Both let Claude, ChatGPT or Cursor use ComplyCube. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every ComplyCube call.
How is Elaichi different from Composio for ComplyCube?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to ComplyCube: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put ComplyCube in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot