Skip to content

OneTrust MCP connector

Connect OneTrust to Claude, ChatGPT, Cursor, or the Elaichi Agent through Elaichi, so your team can log data subject requests, track AI governance entities and tasks, and review consent banners and preferences inside their own OneTrust access.

  • How it connects. App credentials. 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 OneTrust to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect OneTrust once

  1. Open Connections, choose Add connection, and pick OneTrust.

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

  3. Paste your OneTrust app credentials. OneTrust authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

onetrust
OneTrust
Alloy
Cakewalk
Comp AI
ComplyCube
Drata
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.

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

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

OneTrust 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 OneTrust 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 OneTrust through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Privacy

    Log a data subject request as it arrives

    When someone emails asking for a copy of their data, describe the request in plain language and the agent opens the data subject access request in OneTrust for you.

  • AI governance

    Register a new AI system in the inventory

    After a vendor demo or an internal build, add the model or use case as an AI governance entity in OneTrust with its type and details filled in, then link it to the systems it relates to.

  • Legal

    Check what is on record before a review

    Search OneTrust for an AI governance entity by name and read back its details and links before the meeting, instead of clicking through the inventory yourself.

  • Compliance

    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.

  • Marketing

    Review the consent banners in play

    List the cookie banners configured in OneTrust and confirm which version each site carries before a campaign or site launch.

  • Security

    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.

Try asking

  • “Summarize AI governance entities created this quarter by type”
  • “List governance entities still sitting in review stages”
  • “Which teams own the most OneTrust governance links”

See all 622 OneTrust tools below

Compare

Elaichi vs Zapier MCP vs Composio for OneTrust

All three can connect OneTrust 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 OneTrust, 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 OneTrust tools Allow or restrict single OneTrust 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 OneTrust 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

OneTrust tools for your AI agents

622 tools are ready to call through Elaichi's MCP endpoint the moment you connect OneTrust, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Showing 244 of 622 OneTrust tools here. Connect OneTrust and call search_tools or tools/list over the MCP endpoint for the complete set.

See it in Elaichi

What connecting OneTrust gets you

6 screens from the product, each doing one job for your OneTrust account.

The agent

Ask about OneTrust records in plain language.

The agent reads live OneTrust governance entities, stages and links to answer.

  • governance entities
  • entity types
  • links
  • stages

Ask Elaichi to work across your apps.

Summarize AI governance entities created this quarter by type

List governance entities still sitting in review stages

Which teams own the most OneTrust governance links

Also runs in Claude, ChatGPT or Cursor

MCP clients

One OneTrust endpoint for every MCP client.

Claude, ChatGPT and Cursor connect over OAuth, no SDK, no shared 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

622 OneTrust tools ready without custom code.

Governance entities, entity types, links and stages, each with full read and write methods.

  • Create a OneTrust type stage
  • Create a OneTrust AI governance entity
  • OneTrust AI governance entities search
  • Get single OneTrust AI governance entity by ID
ElaichiTools
Tool Action Description
Create a OneTrust type stage Create Update the workflow stage for a specific OneTrust incident by entity ID and workflow type. Returns: id, name, description. Required: entity_id, type, nextStageName.
Create a OneTrust AI governance entity Create Create a new AI Governance entity in OneTrust (Models, Datasets, AI Systems, or AI Agents). Returns: id, number, name, orgGroupId, schemaId, entityType, workflowAndStage, entityDetail, attributes, auditFields. Required: name.
OneTrust AI governance entities search Search Search AI Governance entities in OneTrust by full-text query and filters. Returns a paginated list of entities, each with id, number, name, orgGroupId, schemaId, entityType, entityDetail, attributes, and auditFields. Supports Models, Datasets, AI Systems, and AI Agents.
Get single OneTrust AI governance entity by ID Get Get a single AI Governance entity in OneTrust by id. Returns: id, example, name. Required: id.
Update a OneTrust AI governance entity by ID Update Partially update an existing AI Governance entity in OneTrust. Returns: id, number, name, schemaId, entityType. Required: id.

Toolboxes

Every team gets its own OneTrust toolbox.

Curate one toolbox per team so each sees only the OneTrust tools it needs.

  • Privacy
  • Legal
  • Security
  • AI Governance
ElaichiToolboxes
Name Source template Tools Created

Privacy toolbox

OneTrust · governance entities and stages

OneTrust starter 18 Mar 4, 2026

Legal toolbox

OneTrust · records and review approvals

— 9 Mar 2, 2026

Security toolbox

OneTrust · entity types and risk links

— 24 Feb 27, 2026

AI Governance toolbox

OneTrust · AI entities and schema attributes

OneTrust starter 6 Feb 19, 2026

Data Engineering toolbox

OneTrust · entity links and metadata

— 31 Jan 30, 2026

Internal Audit toolbox

OneTrust · stage history and evidence

— 12 Jan 22, 2026

Shared connections

Teammates use OneTrust without seeing credentials.

Each connection shows who linked the OneTrust account and which teams and members share it.

  • Privacy EMEA
  • Legal
  • Security
  • AI Governance
ElaichiConnections
Connection Scope Status Access
ON

OneTrust (Privacy EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
ON

OneTrust (Legal)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
ON

OneTrust (Security)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
ON

OneTrust (AI Governance)

Connected by Tyler Reed

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

OneTrust (Internal Audit)

Connected by Ryan Hayes

Personal • Active Not shared
ON

OneTrust (Data Office)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every OneTrust call is written down.

When, who, what happened, type and resource, appended for each OneTrust action.

  • 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

OneTrust Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

OneTrust Governance entities Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

OneTrust Governance entities 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 turns OneTrust records into decisions.

Fetch governance entities, group them, draft a digest, approve, post back to OneTrust.

OneTrust digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch governance entities

    OneTrust

    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

    OneTrust

    Queued

Collections and dashboards

OneTrust health arrives before anyone asks.

Four metrics, 14 days of entities created and a team breakdown, refreshed on schedule.

OneTrust health

Refreshed 4 minutes ago · every 15 minutes · from the governance entities collection

Live

Governance entities

1,284 ↓ 12%

Entity types

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Governance entities created

Last 14 days

By team

Share of activity

Privacy EMEA 34%

Legal 27%

Security 21%

AI Governance 18%

FAQ

Frequently asked questions

How do I connect OneTrust to Claude?

Two steps. First, connect OneTrust in Elaichi: OneTrust uses app credentials, so you enter the credentials your OneTrust administrator gives you once, and there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. From that point Claude can work in OneTrust as you.

Does OneTrust work with ChatGPT and Cursor as well as Claude?

Yes. Once OneTrust 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 OneTrust once and every client you use picks it up.

What can an AI agent actually do with my OneTrust data?

With OneTrust connected, an agent can open a data subject access request, register an AI system as an AI governance entity, search the inventory and read a system's details, link related systems, and create or update AI governance tasks. It can also list the consent banners, preferences, and audit event types configured in OneTrust. Because OneTrust has a large number of actions, short concrete asks such as "create a task for the fraud model review" work better than long paragraphs.

Does connecting OneTrust give the AI access to everything in the workspace?

No. Every call to OneTrust runs as the person who signed in, so the agent sees only the entities, requests, and settings that person's OneTrust role already allows. Elaichi can narrow that access further with restrictions, and it can never widen it beyond what OneTrust itself grants.

Can my team share one OneTrust connection?

Yes. One person connects OneTrust in Elaichi and shares it with a team, and nobody else ever handles the OneTrust credentials. Each teammate still signs in to Elaichi as themselves, so every action in OneTrust is recorded in the audit log under their own name.

Can I stop an agent from deleting or changing things in OneTrust?

Yes. Restrictions in Elaichi work per action, so you can allow searching and reading OneTrust records while blocking deleting an AI governance entity or removing a link. A blocked action is never advertised to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.

What happens to a OneTrust connection when someone leaves?

Offboarding a person in Elaichi ends their access to OneTrust through every client at once. A OneTrust connection shared with the team keeps working for everyone else. If you disconnect OneTrust in Elaichi, it is removed from Claude, ChatGPT, Cursor, and every other client in one step.

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

Yes. OneTrust 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 OneTrust?

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

How is Elaichi different from Composio for OneTrust?

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

Put OneTrust 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.