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.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
63 tools
How to connect
How to connect ComplyCube to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect ComplyCube once
-
Open Connections, choose Add connection, and pick ComplyCube.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a ComplyCube API key. One person generates a token in ComplyCube and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
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 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 today. 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.
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.
Use cases
What teams do with ComplyCube through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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?”
Compare
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 | $15 per user per month. | 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.
AI tools
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.
See it in Elaichi
What connecting ComplyCube gets you
6 screens from the product, each doing one job for your ComplyCube account.
The agent
Ask about ComplyCube clients in plain language.
Answers come from live ComplyCube clients, documents and risk profiles.
- clients
- addresses
- documents
- risk profiles
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor reach ComplyCube.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
All 63 ComplyCube tools are ready here.
Clients, addresses, documents and risk profiles, with no custom code to write.
- Create a ComplyCube client
- Get single ComplyCube client by ID
- Update a ComplyCube client by ID
- Delete a ComplyCube client by ID
ElaichiToolsToolboxes
Each team gets its own ComplyCube toolbox.
Compliance, Onboarding and Risk each see the ComplyCube tools their work needs.
- Compliance
- Onboarding
- Risk
- Support
ElaichiToolboxesShared connections
Share a ComplyCube account, never the key.
Teammates screen clients and documents through a connection without seeing a credential.
- Compliance EMEA
- Onboarding
- Risk Review
- Support
ElaichiConnectionsAudit log
Every ComplyCube call is written down.
When, who, what happened, type and resource, in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule runs your ComplyCube review.
Fetch clients, group them, draft a digest, approve it, post back to ComplyCube.
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 Michael Brennan
Approve Deny -
Post the digest
ComplyCube
Queued
Collections and dashboards
ComplyCube health, counted on a schedule.
Four metrics, 14 days of clients created, and a breakdown by team.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 blocking 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 blocking deletion, redaction or updates. A blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it.
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 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.