Skip to content

Cortex MCP connector

The Cortex connector brings your service catalog, custom data, and custom events into Claude, ChatGPT, Cursor, Microsoft Copilot, and any MCP client, so each engineer can look up and update Cortex entities inside their own access, with every call logged.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Which Cortex catalog entities have no owner set?

Working in Cortex with Elaichi

  • List all Cortex API key
  • Get single Cortex API key by ID
  • List all Cortex catalog entity
Ask anything…
Governance / Audit log Last 24 hours
Cortex List all Cortex catalog entity Emily Carter · Claude · 9:41 AM Done
Cortex Get single Cortex API key by ID Emily Carter · Claude · 9:41 AM Done
Cortex List all Cortex API key Emily Carter · Claude · 9:41 AM Done
Cortex Create a Cortex API key Megan Brooks · ChatGPT · 9:38 AM Done
Cortex Update a Cortex API key by ID Ryan Hayes · Cursor · 9:35 AM Done

How to connect Cortex to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

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

Cortex MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Cortex 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. The plugin directory lives at chatgpt.com/plugins.

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

Cortex MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Cortex 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.

What teams do with Cortex through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Cortex is logged.

  • Platform engineering

    Find who owns a service before paging

    Ask which Cortex catalog entity backs a failing service and pull its owner and details before you page anyone at two in the morning.

  • Engineering

    Catch the catalog up after a migration

    When a system is retired or split, archive the old Cortex entities and unarchive the ones coming back, in one plain request rather than a dozen clicks.

  • Site reliability

    Record deploys and incidents as events

    Log a deploy or an incident as a custom event against the right Cortex entity, then list the last week of events when writing the postmortem.

  • Security

    Track compliance facts per service

    Attach custom data such as data classification or last penetration test date to each Cortex entity, and pull it back by key when an auditor asks.

  • Engineering management

    Update service metadata in bulk

    Push a sheet of service tiers or cost center codes into Cortex custom data in one bulk upsert instead of editing entities one at a time.

  • DevOps

    Clean up stale entities and events

    List Cortex catalog entities that no longer map to anything running, delete the ones that are gone, and clear out old custom events for an entity.

Try asking

  • “Which Cortex catalog entities have no owner set?”
  • “Show scorecard scores for payments services this week.”
  • “List Cortex API keys created in the last month.”

See all 494 Cortex tools →

What connecting Cortex gets you

6 screens from Elaichi, each doing one job for your Cortex account.

Elaichi Agent

Ask Elaichi to work across your apps.

Which Cortex catalog entities have no owner set?

Show scorecard scores for payments services this week.

List Cortex API keys created in the last month.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about catalog entities, get answers.

Plain language questions answered from live Cortex catalog entities and scorecards.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

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

AI apps

Claude, ChatGPT, Cursor and Microsoft Copilot reach Cortex.

One governed MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiTools
Tool Action Description
List all Cortex API key List List API keys in Cortex. Returns each key's cid, createdDate, name, last4, expirationDate, and roles. No required parameters.
Get single Cortex API key by ID Get Get a Cortex API key by id. Returns: description, name, role. Required: id.
Create a Cortex API key Create Create a new Cortex API key. Returns the created key including apiKey (only shown once), name, description, expirationDate, and roles. Required: name, roles.
Update a Cortex API key by ID Update Update a Cortex API key by id. Returns the updated key with cid, createdDate, last4, name, roles, and optional description/expirationDate. Required: id, name.
Delete a Cortex API key by ID Delete Delete a Cortex API key by id. Returns an empty 204 response on success. Required: id.

Tool catalog

494 Cortex tools ready on connect.

Catalog entities, scorecards, custom data and API keys, with no custom code.

ElaichiToolboxes
Name Source template Tools Created

Platform Engineering toolbox

Cortex · catalog entities and ownership

Cortex starter 18 Mar 4, 2026

Service Reliability toolbox

Cortex · scorecards and service health

— 9 Mar 2, 2026

Product Engineering toolbox

Cortex · services and dependencies

— 24 Feb 27, 2026

Developer Experience toolbox

Cortex · custom data and scorecard rules

Cortex starter 6 Feb 19, 2026

Security toolbox

Cortex · API keys and access

— 31 Jan 30, 2026

Engineering Leadership toolbox

Cortex · scorecard reporting by team

— 12 Jan 22, 2026

Toolboxes

Each team gets its own toolbox.

Curate Cortex toolboxes per team so platform and product engineers see different tools.

ElaichiConnections
Connection Scope Status Access
CO

Cortex (Platform)

Connected by Emily Carter

Personal • Active 1 team · 6 members
CO

Cortex (Payments Services)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
CO

Cortex (Developer Experience)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
CO

Cortex (Security)

Connected by Tyler Reed

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

Cortex (Mobile)

Connected by Ryan Hayes

Personal • Active Not shared
CO

Cortex (Data Engineering)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates use Cortex without the credential.

See who connected each Cortex account and how many teams and members share it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Cortex Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Cortex Catalog entities Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Cortex Catalog entities List Toolbox

Audit log

Every Cortex call is on the record.

When, who, what happened, type and resource for each archive, upsert and delete.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

Cortex digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch catalog entities

    Cortex

    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 Jake Morgan

    Approve
  6. Post the digest

    Cortex

    Queued

Automations

A schedule fires, Cortex work finishes.

Fetch catalog entities, group them, draft a digest, approve, post back to Cortex.

Cortex health

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

Live

Catalog entities

1,284 ↓ 12%

Scorecards

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Catalog entities created

Last 14 days

By team

Share of activity

Platform 34%

Payments Services 27%

Developer Experience 21%

Security 18%

Collections and dashboards

Cortex health arrives before you ask.

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

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Cortex

All three can connect Cortex 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 Cortex, 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 Cortex tools Allow or restrict single Cortex 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 Cortex 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 Free for one person; $15 per user per month on Gold. 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.

Cortex tools for your AI agents

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

Showing 326 of 494 Cortex tools here. Connect Cortex and call search_tools or tools/list over the MCP endpoint for the complete set.

Questions, answered

How do I connect Cortex to Claude?

Connecting Cortex to Claude takes two steps. First, connect Cortex in Elaichi by pasting a Cortex API key, 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 the endpoint https://api.elaichi.ai/mcp. Claude will then work with your Cortex service catalog, custom data, and custom events.

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

Yes. Once Cortex is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Cortex once and every client your team uses picks it up.

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

With Cortex connected, an agent can look up a catalog entity and its owner, archive or unarchive entities, attach or read custom data such as tier or on-call team, and record or list custom events like deploys and incidents. It can also do bulk work, such as upserting custom data for many services at once or deleting a batch of retired entities. Because Cortex exposes several hundred actions, short concrete asks such as "archive the payments-legacy entity" work better than long paragraphs.

Does connecting Cortex give the AI everything in my catalog?

No. The AI only reaches what the Cortex API key used to connect can reach, and each person signs in to Elaichi as themselves, so every call to Cortex runs under that person's access. Elaichi can narrow that further, for example limiting a team to reading catalog entities and custom data, but it can never widen access beyond what Cortex already allows.

Can my team share one Cortex connection?

Yes. One person connects Cortex in Elaichi with an API key and shares the connection with a team, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log records who looked up or changed each Cortex entity, event, or custom data value.

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

Yes. Restrictions in Elaichi work per action, so you can allow reading Cortex catalog entities and custom events while restricting deletes, bulk deletes, or archiving. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.

What happens to a Cortex connection when someone leaves?

When a person is offboarded in Elaichi, their access to Cortex through Elaichi ends at once, in every client they had connected. A shared Cortex connection keeps working for everyone else on the team. If you disconnect Cortex in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client in one step.

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

Yes. Cortex 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, Microsoft Copilot, 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 Cortex?

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

How is Elaichi different from Composio for Cortex?

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

Put Cortex in front of your team

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

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot