CrowdStrike MCP connector
Connect CrowdStrike to Elaichi and Claude, ChatGPT, Cursor and Microsoft Copilot can list users, review roles and access scopes, and manage admission control policies, every request running as the person who asked and landing in the audit log.
- App credentials
- Free 14-day trial
- No credit card
List every CrowdStrike user with the administrator role
Working in CrowdStrike with Elaichi
-
List all CrowdStrike users
-
Get single CrowdStrike user by ID
-
List all CrowdStrike roles
How to connect CrowdStrike to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
CrowdStrike 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.
CrowdStrike 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.
CrowdStrike 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.
CrowdStrike 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.
CrowdStrike 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 CrowdStrike 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 CrowdStrike through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in CrowdStrike is logged.
-
Security operations
Find out who holds admin roles
Ask for every CrowdStrike user with an administrator role and get the list back in seconds, without clicking through the console. Follow up with what access scopes that role actually carries.
-
IT
Grant a new analyst the right roles
When someone joins the SOC, look up their CrowdStrike user and grant the roles the team agreed on in one request. Confirm the result before you close the ticket.
-
IT
Revoke CrowdStrike access the day someone leaves
Pull the leaver's roles, revoke them, and remove the user from CrowdStrike as part of the offboarding checklist. The audit log records who did it and when.
-
Compliance
Produce a user and role listing for auditors
Export every CrowdStrike user, the roles they hold and the scopes behind those roles, ready for a quarterly access review. Repeat it next quarter with the same ask.
-
Platform engineering
Review admission control policies before a release
List the admission control policies and rule groups that apply to a cluster and check their precedence before a deploy. Spot a stale custom rule before it rejects a workload.
-
Platform engineering
Add a host group to a policy
Attach a new cluster host group to an existing admission control policy, or remove one that was decommissioned, without opening the CrowdStrike console. Update the policy and confirm the change in the same conversation.
Try asking
- “List every CrowdStrike user with the administrator role”
- “Which admission control policies apply to the production host group?”
- “Revoke the analyst role from Priya and confirm her remaining roles”
What connecting CrowdStrike gets you
6 screens from Elaichi, each doing one job for your CrowdStrike account.
Ask Elaichi to work across your apps.
List every CrowdStrike user with the administrator role
Which admission control policies apply to the production host group?
Revoke the analyst role from Priya and confirm her remaining roles
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask who holds admin rights, get answers.
Question CrowdStrike users, roles and admission control policies in plain language from live records.
Copy the endpoint
AI apps
One CrowdStrike endpoint for every MCP client.
Claude, ChatGPT and Cursor reach CrowdStrike through one governed endpoint, no SDK, no shared API key.
Tool catalog
1568 CrowdStrike tools, no code to write.
Users, roles, access scopes and admission control policies, covered without a line of custom code.
Toolboxes
Every team gets its own CrowdStrike toolbox.
Scope a toolbox to security operations, another to platform engineering, each with what it needs.
Shared connections
Share CrowdStrike without sharing a credential.
One person connects CrowdStrike, teammates work through it, and nobody else sees the key.
Audit log
Know who touched which CrowdStrike policy.
Every user, role and policy change lands in the log with who, when and what.
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.
CrowdStrike digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
CrowdStrike
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
CrowdStrike
Queued
Workflows
A schedule starts CrowdStrike work, a person approves.
Fetch new admission control policies, group them, draft a digest, approve it, post it back.
CrowdStrike health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Roles
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Security operations 34%
Platform engineering 27%
IT helpdesk 21%
Compliance 18%
Collections and dashboards
CrowdStrike health numbers, computed, not asked for.
Users, roles and policies over 14 days, by team, refreshed on a schedule, no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for CrowdStrike
All three can connect CrowdStrike 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 CrowdStrike tools | Allow or restrict single CrowdStrike 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 CrowdStrike 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.
CrowdStrike tools for your AI agents
1568 tools are ready to call through Elaichi's MCP endpoint the moment you connect CrowdStrike, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 380 of 1568 CrowdStrike tools here. Connect CrowdStrike and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
How do I connect CrowdStrike to Claude?
Connect CrowdStrike in Elaichi by signing in with your CrowdStrike app credentials. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your CrowdStrike users, roles and admission control policies are ready to ask about.
Does CrowdStrike work with ChatGPT and Cursor as well as Claude?
Yes. CrowdStrike connects to Elaichi once, and 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 CrowdStrike one time and every client you use picks it up.
What can an AI agent actually do with my CrowdStrike data?
An agent can list your CrowdStrike users and the roles each one holds, look up a single user, grant or revoke a role, and show which access scopes a role carries. On the Kubernetes side it can list and review admission control policies, add or remove host groups and custom rules, and create or update a policy or rule group. Short, concrete asks work best: who in CrowdStrike has the administrator role gets a cleaner answer than a long paragraph.
Does connecting CrowdStrike give the AI everything in my Falcon environment?
No. Access follows the person who signed in to Elaichi and the CrowdStrike connection they were given, so the agent sees only what those CrowdStrike roles and access scopes allow. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what CrowdStrike itself permits.
Can I stop an agent from deleting or changing things in CrowdStrike?
Yes. In Elaichi you can restrict any single CrowdStrike action, such as deleting a user, revoking a role or deleting an admission control policy, for a role or 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 CrowdStrike connection when someone leaves?
When someone leaves, offboarding them in Elaichi ends their access to CrowdStrike through every client at once. A CrowdStrike connection shared with the team keeps working for everyone else. If you want it gone entirely, disconnecting CrowdStrike once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the CrowdStrike MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. CrowdStrike 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 CrowdStrike?
Yes. Both let Claude, ChatGPT or Cursor use CrowdStrike. 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 CrowdStrike call.
How is Elaichi different from Composio for CrowdStrike?
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 CrowdStrike: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put CrowdStrike 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