Compliance
Comp AI MCP connector
The Comp AI connector brings your compliance program into Claude, ChatGPT, Cursor, and other MCP clients, so your team can check people, devices, training, and employment evidence in Comp AI by asking in plain language.
-
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.
How to connect
How to connect Comp AI to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Comp AI once
-
Open Connections, choose Add connection, and pick Comp AI.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Comp AI API key. One person generates a token in Comp AI 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.
Connect Comp AI to 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.
Connect Comp AI to 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.
Connect Comp AI to 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 Comp AI 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 Comp AI through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Compliance
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.
-
IT
Check which devices are registered to whom
Pull the devices linked to each person in Comp AI to confirm laptops are enrolled before an access review or a hardware refresh.
-
People
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.
-
Security
See how tests are doing by owner
Ask for test results grouped by assignee to spot which owners have failing or stale checks and who to nudge first.
-
Operations
Gather employment evidence for a control
Collect the employment evidence Comp AI holds for a group of people when an auditor asks you to prove offboarding or onboarding was handled correctly.
-
Leadership
Keep organization details and roles current
Update your Comp AI organization details, adjust who receives role notifications, or hand ownership to a new compliance lead as the team changes.
Try asking
- “Which Comp AI organizations still have onboardings unfinished?”
- “List Comp AI API keys created in the last month.”
- “Who was added to Comp AI people this week?”
AI tools
Comp AI tools for your AI agents
248 tools are ready to call through Elaichi's MCP endpoint the moment you connect Comp AI, 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 Comp AI gets you
6 screens from the product, each doing one job for your Comp AI account.
The agent
Ask in plain language, read live Comp AI records.
Questions about organizations, people and API keys answered from live Comp AI records.
- organizations
- people
- onboardings
- api keys
Ask Elaichi to work across your apps.
Which Comp AI organizations still have onboardings unfinished?
List Comp AI API keys created in the last month.
Who was added to Comp AI people this week?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Every client reaches Comp AI over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
248 Comp AI tools ready, no custom code.
Organizations, onboardings, role notifications and API keys, each with named resources and methods.
- List all Comp AI organizations
- Update a Comp AI organization by ID
- List all Comp AI organization onboardings
- Create a Comp AI organization transfer ownership
Toolboxes
Every team gets its own Comp AI toolbox.
Curate one toolbox per team so Compliance and IT see different Comp AI tools.
- Compliance
- Security
- IT
- People Ops
Shared connections
Teammates use Comp AI without seeing credentials.
The connections table shows who connected each account and which teams and members share it.
- Compliance
- Security
- IT Operations
- People Ops
Audit log
Answer who changed which Comp AI record.
Every call lands append only with time, actor, action, type and resource.
- When
- Who
- What happened
- Type
Launching 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 fires and Comp AI work finishes.
Six steps fetch organizations, group them, draft a digest, take approval, post back.
Comp AI digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch organizations
Comp AI
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
Comp AI
Queued
Collections and dashboards
Comp AI health numbers arrive without asking.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
Comp AI health
Refreshed 4 minutes ago · every 15 minutes · from the organizations collection
Organizations
1,284 ↓ 12%
People
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Organizations created
Last 14 days
By team
Share of activity
Compliance 34%
Security 27%
IT Operations 21%
People Ops 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Comp AI to Claude?
Connect Comp AI in Elaichi first, which asks for a Comp AI API key from your Comp AI settings, then paste https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add. There is no OAuth application to register and no client ID or secret to generate. Once it is added, Claude signs you in through Elaichi and Comp AI is ready to use in your conversations.
Does Comp AI work with ChatGPT and Cursor as well as Claude?
Yes. Comp AI is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You do not set Comp AI up again for each client.
What can an AI agent actually do with my Comp AI data?
With Comp AI connected, an agent can look up people and their devices, see who has finished training videos, review test results by assignee, and gather employment evidence for a control. It can also add people one at a time or in bulk, resend portal invites, and update your organization details or role notifications. Comp AI has a lot of ground to cover, so short, specific asks like "list people with unfinished training" work better than long paragraphs.
Does connecting Comp AI give the AI access to my whole organization?
No. Every request to Comp AI through Elaichi runs as the person who signed in, so the agent sees only the organizations, people, and evidence that person's Comp AI access already allows. Elaichi can narrow that further with restrictions, but it can never grant more than the person already has in Comp AI.
Can I stop an agent from deleting or changing things in Comp AI?
Yes. Restrictions in Elaichi work per action, so you can allow reading people, devices, and test results in Comp AI while blocking deletions, bulk creates, or organization changes. A blocked action is never shown to Claude, ChatGPT, or any other client, so no prompt can reach it.
What happens to a Comp AI connection when someone leaves?
Offboarding the person in Elaichi ends their access to Comp AI through every client at once, and the audit log keeps a record of what they did while they had it. A shared Comp AI connection keeps working for everyone else on the team. If you ever want Comp AI gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.
Put Comp AI in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.