Skip to content

Connectors / Compliance

Compliance MCP connectors for Claude, ChatGPT and Cursor

10+ Compliance connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.

Start 14-day free trial Browse the full catalog
https://api.elaichi.ai/mcp The same for every user.

  • Their own access. An agent never gets more than the person it acts for.

  • One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.

The connectors

Compliance connectors in the catalog

Connect one and your whole team reaches it, each inside the access they already have, without anyone handling a credential.

11 connectors

Browse all 400+ connectors →

In practice

What teams do with Compliance connectors

Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.

Compliance

  • OneTrust

    Assign and update AI review tasks

    Create a OneTrust AI governance task for the owner of a system, then update its status and notes straight after the review call.

  • Comp AI

    Find who still owes training before the audit

    Ask which people in Comp AI have not finished their security training videos and get a list you can chase, without opening every profile.

  • Vanta

    Find every control still missing an owner

    Ask which Vanta controls have no owner assigned, then set the right person on each one without opening every record by hand.

IT

  • Drata

    Check who is in Drata and who is not

    Compare the Drata personnel list against the new hires and leavers from last month so nobody is missing from onboarding checks or lingering after they left.

  • Lumos

    Answer who has access to what

    Ask which accounts a person holds across every app in Lumos, or which people hold accounts in one app, without opening a single admin console.

  • Secureframe

    Review devices and bring them into scope

    See every laptop and workstation Secureframe is tracking, check which ones fall under a given framework, and put a new hire's machine in scope the same afternoon.

Security

  • Cakewalk

    Deactivate a leaver and remove group access

    When someone leaves, deactivate their Cakewalk user and pull them out of the user groups that grant work apps, all in one conversation.

  • Sprinto

    Attach evidence the moment work is done

    After a review or a fix is finished, add the evidence to the right Sprinto workflow check while it is still fresh, instead of leaving it for the week before the audit.

  • OneTrust

    Prepare for an audit in minutes

    Pull the list of audit event types OneTrust tracks and the preference settings in place, so you know what evidence exists before the auditors ask.

People

  • Comp AI

    Add new hires in one go

    Give the agent the names and emails from this week's start list and it creates them as people in Comp AI in bulk, then resends portal invites to anyone who has not accepted.

  • Drata

    Kick off background checks on day one

    When a new hire is added, start their background check in Drata straight away instead of waiting for someone to remember the compliance step.

  • Cakewalk

    Set up a new hire's apps on day one

    Add the new starter to the right Cakewalk user group and grant the group's default work apps in one go instead of app by app.

Once it is connected

Things to ask

Each of these is answered against the access the person asking already has, in the Compliance account you connected.

  • List open Alloy cases created this week by reviewer.

    Alloy

  • List Cakewalk users in the Finance group.

    Cakewalk

  • Which Comp AI organizations still have onboardings unfinished?

    Comp AI

  • Show ComplyCube clients with a high risk profile

    ComplyCube

  • List open audit requests for our SOC 2 audit.

    Drata

  • List Lumos apps added in the last 30 days.

    Lumos

  • Summarize AI governance entities created this quarter by type

    OneTrust

  • List all Secureframe repositories missing a framework asset scope.

    Secureframe

The tools

What an agent can call in Compliance

Connectors
10+

in the Compliance catalog

Tools
1,594

callable the moment you connect

Hosted sign-in
11

connect with nothing to register

Of those 1,594 tools, 8% delete something. Restricting an agent to reads is not a promise here, it is 680 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.

Read 43%
680 tools · list, get, search
Write 32%
513 tools · create, update, send
Delete 8%
120 tools · delete, remove, archive
Other 18%
281 tools · vendor-specific verbs

One endpoint

https://api.elaichi.ai/mcp

Every connector above answers here.

Every Compliance connector, by depth

Tool counts are what the connector exposes today; the split is what those tools do.

Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect.

Compliance connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
OneTrust 622 Hosted
Comp AI 248 Hosted
Vanta 182 Hosted
Drata 165 Hosted
Alloy 138 Hosted
Lumos 88 Hosted
ComplyCube 63 Hosted
Secureframe 57 Hosted
Cakewalk 25 Hosted
Sprinto 5 Hosted
Veeva Vault 1 Hosted

FAQ

Frequently asked questions

How many Compliance connectors does Elaichi have?

10+ Compliance connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.

Can Claude, ChatGPT and Cursor all use Compliance connectors?

Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent all connect to that same address with OAuth. Connecting a Compliance account once makes it reachable from every one of them.

Do Compliance connectors work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Compliance connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.

Do Compliance connectors need me to bring my own OAuth app?

No. Every Compliance connector in the catalog connects through Elaichi's hosted sign-in, so there is nothing to register before you start.

Can I stop an agent from writing to Compliance tools?

Yes. Tool restrictions apply at role and individual level, and a restricted tool is never advertised to the model, so it cannot be called or guessed at from the tool list. Read-only access to a Compliance connector is a matter of allowing the reads and leaving the writes out.

Whose access does an agent get on a shared Compliance connection?

The access of the person the agent is acting for, resolved against their current role on every call — not the access of whoever connected the account. A colleague can use a connection without ever seeing its credential.

Nearby

Teams that connect Compliance usually connect these too

Put Compliance connectors in front of your team

14 days on Gold, no credit card. Connect one and pick what each team can call.

Start free trial Talk to us
Works with
Claude ChatGPT Cursor 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.