Skip to content

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.

1

In Elaichi

Connect Comp AI once

  1. Open Connections, choose Add connection, and pick Comp AI.

  2. Optionally set Share with to give a team access, then press Connect.

  3. 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.

comp ai
Comp AI
Alloy
Cakewalk
ComplyCube
Drata
LawVu
2

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.

Comp AI MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Comp AI MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Comp AI MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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?”

See all 248 Comp AI tools below

Compare

Elaichi vs Zapier MCP vs Composio for Comp AI

All three can connect Comp AI to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Comp AI, by what to check
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 Comp AI tools Allow or restrict single Comp AI 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 Comp AI 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

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.

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.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

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
ElaichiTools
Tool Action Description
List all Comp AI organizations List Retrieve the compai organization profile used to personalize compliance workflows, Trust Center branding, and audit readiness reporting. Returns: id, name, slug, logo, website, onboardingCompleted, hasAccess, primaryColor, createdAt, and authType.
Update a Comp AI organization by ID Update Partially update the authenticated organization in compai; only the fields you supply are changed. Returns: id, name, slug, logo, website, onboardingCompleted, hasAccess, primaryColor, createdAt, and authType.
List all Comp AI organization onboardings List Get the organization onboarding status in Comp AI. Returns the onboarding configuration including profile, api_keys, logo, ownership, role_notifications, and access_approval settings.
Create a Comp AI organization transfer ownership Create Transfer organization ownership to another member in compai. The current owner becomes an admin and the new member receives the owner role. Returns: success, message, currentOwner (with memberId, previousRoles, newRoles), and newOwner (with memberId, previousRoles, newRoles). Required: newOwnerId.
List all Comp AI organization role notifications List Get the current role notification settings for the organization in Comp AI. Returns: settings (an array of per-role notification preferences, each containing role, policyNotifications, taskReminders, taskAssignments, taskMentions, weeklyTaskDigest, and findingNotifications).

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
ElaichiToolboxes
Name Source template Tools Created

Compliance toolbox

Comp AI · organizations and onboardings

Comp AI starter 18 Mar 4, 2026

Security toolbox

Comp AI · API keys and revocations

— 9 Mar 2, 2026

IT toolbox

Comp AI · people and access approvals

— 24 Feb 27, 2026

People Ops toolbox

Comp AI · people and role notifications

Comp AI starter 6 Feb 19, 2026

Audit toolbox

Comp AI · organizations and evidence reads

— 31 Jan 30, 2026

Leadership toolbox

Comp AI · organization ownership transfers

— 12 Jan 22, 2026

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
ElaichiConnections
Connection Scope Status Access
CO

Comp AI (Compliance)

Connected by Emily Carter

Personal • Active 1 team · 6 members
CO

Comp AI (Security)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
CO

Comp AI (IT Operations)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
CO

Comp AI (People Ops)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
CO

Comp AI (Internal Audit)

Connected by Ryan Hayes

Personal • Active Not shared
CO

Comp AI (Customer Trust)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

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
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Comp AI Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Comp AI Organizations Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Comp AI Organizations List Toolbox

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 Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch organizations

    Comp AI

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. 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

Live

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%

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 my team share one Comp AI connection?

Yes. One person connects Comp AI in Elaichi and shares it with a team, and nobody else ever handles the Comp AI API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every change to a person, device, or organization record 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.

Does the Comp AI MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Comp AI 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 Comp AI?

Yes. Both let Claude, ChatGPT or Cursor use Comp AI. 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 Comp AI call.

How is Elaichi different from Composio for Comp AI?

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 Comp AI: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Comp AI in front of your team

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

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.