Product Development
Cortex MCP connector
The Cortex connector brings your service catalog, custom data, and custom events into Claude, ChatGPT, Cursor, and any MCP client, so each engineer can look up and update Cortex entities inside their own access, with every call logged.
-
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 Cortex to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Cortex once
-
Open Connections, choose Add connection, and pick Cortex.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Cortex API key. One person generates a token in Cortex 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 Cortex 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 Cortex 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 Cortex 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 Cortex 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 Cortex through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
No tools match your search.
See it in Elaichi
What connecting Cortex gets you
6 screens from the product, each doing one job for your Cortex account.
The agent
Ask about catalog entities, get answers.
Plain language questions answered from live Cortex catalog entities and scorecards.
- catalog entities
- scorecards
- custom data entries
- api keys
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Cortex.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
494 Cortex tools ready on connect.
Catalog entities, scorecards, custom data and API keys, with no custom code.
- List all Cortex API key
- Get single Cortex API key by ID
- Create a Cortex API key
- Update a Cortex API key by ID
Toolboxes
Each team gets its own toolbox.
Curate Cortex toolboxes per team so platform and product engineers see different tools.
- Platform Engineering
- Service Reliability
- Product Engineering
- Developer Experience
Shared connections
Teammates use Cortex without the credential.
See who connected each Cortex account and how many teams and members share it.
- Platform
- Payments Services
- Developer Experience
- Security
Audit log
Every Cortex call is on the record.
When, who, what happened, type and resource for each archive, upsert and delete.
- 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, Cortex work finishes.
Fetch catalog entities, group them, draft a digest, approve, post back to Cortex.
Cortex digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch catalog entities
Cortex
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
Cortex
Queued
Collections and dashboards
Cortex health arrives before you ask.
Four metrics, 14 days of entities created, and a team breakdown, refreshed on schedule.
Cortex health
Refreshed 4 minutes ago · every 15 minutes · from the catalog entities collection
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 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 blocking deletes, bulk deletes, or archiving. A blocked action is never advertised to Claude, ChatGPT, Cursor, or any other client, so no prompt, accidental or otherwise, can reach it.
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, and every other client in one step.
Put Cortex in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.