Cortex XDR MCP connector
Connect Cortex XDR to Elaichi and your analysts can review alerts, check response actions and track affected software from Claude, ChatGPT, Cursor or Microsoft Copilot, each acting as themselves, with every call logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Summarize the high severity Cortex XDR alerts from the last 24 hours
Working in Cortex XDR with Elaichi
-
Cortex XDR actions get action status
-
List all Cortex XDR affected software
-
Cortex XDR alerts get alerts multi events
How to connect Cortex XDR to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Cortex XDR MCP connector for 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.
Cortex XDR MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
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 XDR MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
Cortex XDR MCP connector for 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.
Cortex XDR MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
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 XDR 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.
What teams do with Cortex XDR 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 XDR is logged.
-
Security operations
Triage the overnight alert queue
Ask for the Cortex XDR alerts that arrived since the last shift, grouped by severity and host, and update their status as you work through them.
-
Incident response
Check whether a response action finished
Find out if the file retrieval you kicked off on a laptop has completed, and pull the details of what came back, without opening the console.
-
Threat hunting
Pull the events behind an alert
Get the full event chain and the packet capture tied to a suspicious alert so you can follow what the process actually did.
-
Vulnerability management
See which software is affected
List the affected software Cortex XDR knows about and ask which packages show up most across open alerts before you plan patching.
-
Application security
Keep the application inventory current
Add, update or import the applications your appsec program tracks in Cortex XDR, and review which assets can still be attached to each one.
-
IT
Audit who holds an API key
List the Cortex XDR API keys in use, see which ones are stale, and retire the ones nobody should still have.
Try asking
- “Summarize the high severity Cortex XDR alerts from the last 24 hours”
- “Which affected software shows up most across open alerts?”
- “Has the file retrieval action on the finance laptop finished?”
What connecting Cortex XDR gets you
6 screens from Elaichi, each doing one job for your Cortex XDR account.
Ask Elaichi to work across your apps.
Summarize the high severity Cortex XDR alerts from the last 24 hours
Which affected software shows up most across open alerts?
Has the file retrieval action on the finance laptop finished?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Cortex XDR alerts in plain words.
Type a question and the agent answers from live alerts, actions and affected software.
Copy the endpoint
AI apps
One endpoint serves Claude, ChatGPT and Cursor.
Every client reaches Cortex XDR through one governed endpoint, with no SDK and no shared key.
Tool catalog
443 Cortex XDR tools, no code to write.
Alerts, actions, affected software, API keys and applications, covered without a line of custom code.
Toolboxes
Every team gets its own Cortex XDR toolbox.
Analysts, responders and appsec each work from a toolbox scoped to their team.
Shared connections
Share one Cortex XDR connection, never the key.
One person connects, teammates work through it, and nobody else ever sees the API key.
Audit log
Every Cortex XDR call lands in the log.
See when, who, what happened and which alert or action was touched.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Cortex XDR digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch alerts
Cortex XDR
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 Jake Morgan
Approve Deny -
Post the digest
Cortex XDR
Queued
Workflows
A schedule drafts the alert digest for you.
New Cortex XDR alerts are fetched, grouped, summarized, approved by a person and posted back.
Cortex XDR health
Refreshed 4 minutes ago · every 15 minutes · from the alerts collection
Alerts
1,284 ↓ 12%
Actions
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Alerts created
Last 14 days
By team
Share of activity
SOC tier 1 34%
SOC tier 2 27%
Incident response 21%
Threat hunting 18%
Collections and dashboards
Cortex XDR health, computed, not asked for.
Four metrics, fourteen days of alerts created and a team breakdown, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Cortex XDR
All three can connect Cortex XDR to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| 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 XDR tools | Allow or restrict single Cortex XDR 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 XDR 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 XDR tools for your AI agents
443 tools are ready to call through Elaichi's MCP endpoint the moment you connect Cortex XDR, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 129 of 443 Cortex XDR tools here. Connect Cortex XDR and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
How do I connect Cortex XDR to Claude?
Connect Cortex XDR in Elaichi first: you paste the API key from your Cortex XDR tenant, and that is the whole sign-in step, with 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. Claude asks you to sign in to Elaichi, and from then on it can reach Cortex XDR as you.
Does Cortex XDR work with ChatGPT and Cursor as well as Claude?
Yes. Once Cortex XDR 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 XDR once and every client picks it up.
What can an AI agent actually do with my Cortex XDR data?
It can list and summarize Cortex XDR alerts, update their status, pull the events and packet capture behind one, and check whether a response action such as a file retrieval has finished. It can also list affected software, manage the applications and assets in your appsec inventory, and review API keys. Short, concrete asks such as 'show me critical alerts from today' work better than long paragraphs.
Does connecting Cortex XDR give the AI access to my whole tenant?
No. Every call to Cortex XDR runs with the role and permissions of the person who signed in, so an agent sees exactly the alerts and settings that person could see in the console. Elaichi can narrow that access further with restrictions, and it can never widen it.
Can I stop an agent from deleting or changing things in Cortex XDR?
Yes. Restrictions in Elaichi work per action, so you can let a role read Cortex XDR alerts but stop it from updating them, deleting API keys or changing applications, and you can set the same for one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Cortex XDR connection when someone leaves?
Offboarding that person in Elaichi ends their access to Cortex XDR at once, in every client they used. A shared Cortex XDR connection keeps working for everyone else on the team. If you ever want it gone entirely, disconnecting Cortex XDR once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the Cortex XDR MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Cortex XDR 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 XDR?
Yes. Both let Claude, ChatGPT or Cursor use Cortex XDR. 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 XDR call.
How is Elaichi different from Composio for Cortex XDR?
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 XDR: 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 XDR 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