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

Source: https://elaichi.ai/connectors/crowdstrike/

## Facts

| | |
| --- | --- |
| Application | CrowdStrike |
| Category | Security |
| AI tools | 1568 |
| Authentication | App credentials |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once CrowdStrike is connected

- 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

## Connect CrowdStrike in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick CrowdStrike.
2. Optionally set Share with, then press Connect.
3. Paste your CrowdStrike app credentials. CrowdStrike authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which CrowdStrike tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## CrowdStrike MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## CrowdStrike MCP connector for Microsoft Copilot

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

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

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

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a CrowdStrike tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with CrowdStrike through Elaichi

### Find out who holds admin roles

Security operations. 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.

### Grant a new analyst the right roles

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

### Revoke CrowdStrike access the day someone leaves

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

### Produce a user and role listing for auditors

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

### Review admission control policies before a release

Platform engineering. 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.

### Add a host group to a policy

Platform engineering. 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.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one CrowdStrike connection?

Yes. One person connects CrowdStrike in Elaichi and shares it with a team, and nobody else ever handles the CrowdStrike credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who listed a user or changed a policy, not a shared account.

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

## All 1568 CrowdStrike tools

Every tool below is callable through https://api.elaichi.ai/mcp once CrowdStrike is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all CrowdStrike users** (List). List user IDs (UUIDs) in the customer account. Returns an array of user UUIDs; use users.get for details. Required API scope: User management: READ.
- **Get single CrowdStrike user by ID** (Get). Get a user's details by user UUID. Required API scope: User management: READ. Required: id.
- **Delete a CrowdStrike user by ID** (Delete). Delete a user permanently. The id is the user UUID. Required API scope: User management: WRITE. Required: id.
- **Update a CrowdStrike user by ID** (Update). Update a user's first and/or last name. The id is the user UUID. Required API scope: User management: WRITE. Required: id.
- **Update a CrowdStrike grant role by ID** (Update). Grant one or more roles to a user. Required API scope: User management: WRITE. Required: uuid, role_ids.
- **Update a CrowdStrike revoke role by ID** (Update). Revoke one or more roles from a user. Required API scope: User management: WRITE. Required: uuid, role_ids.
- **List all CrowdStrike roles** (List). List role IDs available in the customer account. Required API scope: User management: READ.
- **Get single CrowdStrike role by ID** (Get). Get role details by role ID. Required API scope: User management: READ. Required: id.
- **List all CrowdStrike user roles** (List). List the role grants of a user (direct and Flight Control). Required API scope: User management: READ. Required: user_id.
- **CrowdStrike access scopes list access scopes external** (List). List Access Scopes By ID. Required API scope: Access Scope: READ.
- **CrowdStrike access scopes query access scopes external** (Search). Query Access Scopes and returns IDs. Required API scope: Access Scope: READ.
- **Admission control policies admission control add host groups** (Add). Add one or more host groups to an admission control policy. Required API scope: Falcon Container Policies: WRITE. Required: host_groups, id.
- **Admission control policies admission control add custom rule** (Add). Add one or more custom Rego rules to a rule group in an admission control policy. Required API scope: Falcon Container Policies: WRITE. Required: id, rule_groups.
- **Admission control policies admission control create policy** (Create). Create an admission control policy. Required API scope: Falcon Container Policies: WRITE. Required: name.
- **Admission control policies admission control create rule groups** (Create). Create one or more rule groups and add them to an existing admission control policy. Required API scope: Falcon Container Policies: WRITE. Required: id, rule_groups.
- **Admission control policies admission control delete policies** (Delete). Delete an admission control policy. Required API scope: Falcon Container Policies: WRITE. Required: ids.
- **Admission control policies admission control delete rule groups** (Delete). Delete rule groups. Required API scope: Falcon Container Policies: WRITE. Required: policy_id, rule_group_ids.
- **Admission control policies admission control get policies** (Get). Get admission control policies. Required API scope: Falcon Container Policies: READ. Required: ids.
- **Admission control policies admission control query policies** (Search). Search admission control policies. Required API scope: Falcon Container Policies: READ.
- **Admission control policies admission control remove host groups** (Delete). Remove one or more host groups from an admission control policy. Required API scope: Falcon Container Policies: WRITE. Required: policy_id, host_group_ids.
- **Admission control policies admission control remove custom rule** (Delete). Delete one or more custom Rego rules from all rule groups in an admission control policy. Required API scope: Falcon Container Policies: WRITE. Required: policy_id, custom_rule_ids.
- **Admission control policies admission control group selectors** (Action). Replace labels and/or namespaces of a rule group within an admission control policy. Required API scope: Falcon Container Policies: WRITE. Required: id, rule_groups.
- **Admission control policies admission control group precedence** (Action). Change precedence of rule groups within an admission control policy. Required API scope: Falcon Container Policies: WRITE. Required: id, rule_groups.
- **Admission control policies admission control update policy** (Update). Update an admission control policy. Required API scope: Falcon Container Policies: WRITE. Required: ids.
- **Admission control policies admission control policy precedence** (Action). Update admission control policy precedence. Required API scope: Falcon Container Policies: WRITE. Required: id.
- **Admission control policies admission control update rule groups** (Update). Update a rule group. Required API scope: Falcon Container Policies: WRITE. Required: id, rule_groups.
- **CrowdStrike agent invocation get agent invocation v 3** (Get). Get the messages that an invocation produced. Required API scope: Charlotte AI Agent Definition: READ. Required: truto_agent_invocation_id.
- **CrowdStrike agent invocation invoke agent version external v 1** (Action). Invoke a specific agent version by agent ID and version ID with the specified input. Required API scope: Charlotte AI Agent Definition: WRITE. Required: id, messages, version_id.
- **CrowdStrike agent invocation invoke published agent external v 1** (Action). Invoke a published agent by ID with the specified input. Required API scope: Charlotte AI Agent Definition: WRITE. Required: id, messages.
- **CrowdStrike agent invocation patch agent invocation v 3** (Action). Modify an in-flight agent invocation. Required API scope: Charlotte AI Agent Definition: WRITE. Required: id, status.
- **CrowdStrike agent templates entities agent templates v 1** (Action). Retrieve agent template entities for the provided IDs. Required API scope: Charlotte AI Agent Definition: READ. Required: ids.
- **CrowdStrike agent templates queries agent templates v 1** (Action). Query agent template IDs with pagination. Required API scope: Charlotte AI Agent Definition: READ.
- **CrowdStrike agent versions get agent versions v 1** (Get). Retrieve agent version entities for the provided ids. Required API scope: Charlotte AI Agent Definition: READ. Required: ids.
- **CrowdStrike agent versions query agent versions v 1** (Search). Query agent versions based on the provided filters. Required API scope: Charlotte AI Agent Definition: READ.
- **CrowdStrike agents create or edit agent external v 3** (Create). Create or update an agent. Required API scope: Charlotte AI Agent Definition: WRITE. Required: version_definition.
- **CrowdStrike agents delete agent v 1** (Delete). Delete an agent and all of its versions. Required API scope: Charlotte AI Agent Definition: WRITE. Required: truto_agent_id.
- **CrowdStrike agents get agents v 2** (Get). Retrieve agents entities for the provided ids. Required API scope: Charlotte AI Agent Definition: READ. Required: ids.
- **CrowdStrike agents patch agent external v 3** (Action). Modifies existing agents. Required API scope: Charlotte AI Agent Definition: WRITE. Required: truto_agent_id, is_published, version_id.
- **CrowdStrike agents query agents v 2** (Search). Query agents based on the provided filters. Required API scope: Charlotte AI Agent Definition: READ.
- **CrowdStrike aidr aggregate agent sessions v 1** (Action). Aggregate agent-session counts by product. Required API scope: Aidr Events: READ.
- **CrowdStrike aidr aggregate agents v 1** (Action). Aggregate agent counts by product. Required API scope: Aidr Events: READ.
- **CrowdStrike aidr aggregate detections v 1** (Action). Max detection severity per agent and product. Required API scope: Aidr Events: READ.
- **CrowdStrike aidr aggregate skills v 1** (Action). Aggregate skill usage counts by name. Required API scope: Aidr Events: READ.
- **CrowdStrike aidr aggregate skill usage v 1** (Action). Aggregate skill invocation counts by name (LogScale). Required API scope: Aidr Events: READ.
- **CrowdStrike aidr aggregate tools v 1** (Action). Aggregate tool usage counts by name. Required API scope: Aidr Events: READ.
- **CrowdStrike aidr aggregate tool usage v 1** (Action). Aggregate tool invocation counts by name (LogScale). Required API scope: Aidr Events: READ.
- **CrowdStrike aidr entities agent installations v 1** (Action). Get AI agent installation details by IDs. Required API scope: Aidr Events: READ. Required: ids.
- **CrowdStrike aidr entities agent os users v 1** (Action). Get an OS user by aid + username. Required API scope: Aidr Events: READ. Required: aid, username.
- **CrowdStrike aidr entities agent sessions v 1** (Action). Get AI agent session details by IDs. Required API scope: Aidr Events: READ. Required: ids.
- **CrowdStrike aidr entities agents v 1** (Action). Get AI agent details by IDs. Required API scope: Aidr Events: READ. Required: ids.
- ...and 1518 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
