Skip to main content
Activation required. AI access management must be enabled for your tenant before you can use it. To get started, contact the C1 support team for a walkthrough.
The CrowdStrike MCP server lets you govern access to CrowdStrike Falcon — detections, incidents, hosts, vulnerabilities, and other data exposed by the Falcon API — as tools your AI clients can call through C1. CrowdStrike authenticates with a Falcon API client using the OAuth2 client credentials flow. The API client’s client ID and client secret authenticate every user, so all tool calls reach Falcon as one shared identity.

​
How C1 connects to CrowdStrike

C1 hosts the CrowdStrike MCP server, so your users’ AI clients only ever see MCP tools — they never call CrowdStrike directly. When an AI client calls one of these tools, C1 makes the matching request to the CrowdStrike API using the credentials you configure here, then returns the result to the AI client. The credentials you set up below are what C1 uses to call CrowdStrike on your users’ behalf.

​
Before you begin

  • AI access management must be enabled for your tenant. See Enable AI access management.
  • A CrowdStrike Falcon account with the Falcon Administrator role, or another role that can create API clients.
If you don’t see CrowdStrike in your MCP server catalog, contact the C1 support team to enable it for your tenant.

​
Create a CrowdStrike Falcon API client

CrowdStrike issues a client ID and client secret to an API client, which C1 exchanges for an access token using the client credentials flow.
1
In the Falcon console, go to Support and resources > API clients and keys and select Add new API client.
2
Give the client a recognizable name such as C1, then grant Read on the API scopes covering the tools you want. See Choose API scopes for the mapping.
3
Select Create, then copy the Client ID and Client Secret. CrowdStrike shows the secret only once.
4
Note your Falcon cloud’s API base URL, such as https://api.crowdstrike.com or your region-specific endpoint.
For a shared production setup, use a dedicated API client so activity is attributable to C1 rather than a person.

​
Choose API scopes

The API client’s scopes determine which tools return data. C1 exposes tools across several Falcon products, and each needs its own scope. Read covers every list tool: Grant only the scopes for the tools you plan to use. A tool whose scope is missing returns CrowdStrike’s authorization error rather than an empty result, so an unexpected 403 usually means the scope is absent from the API client. The response tools need Write in addition to Read: Leave these scopes off the API client if you want a read-only connection. The tools then return CrowdStrike’s authorization error, so a read-only client is a deliberate way to keep response actions unavailable.
The cloud misconfiguration tools need CSPM registration, not Cloud Security API Detections. The two scopes cover different Falcon APIs, and Cloud Security API Detections does not authorize the tools C1 exposes. If crowdstrike_list_ioms returns 403 while your other tools work, add CSPM registration to the API client.
Scope changes take effect the next time C1 requests a token, so you don’t need to re-register the server or reconnect after editing the API client.

​
How CrowdStrike credentials are shared

The API client authenticates every user as one shared Falcon identity, so CrowdStrike sees a single identity for all tool calls. C1 still attributes each call to the individual user in the AI tool usage audit log. For a shared setup, use a dedicated API client so activity is attributable to C1 rather than a person. For how shared and per-user credentials work across MCP servers, see Configure authentication.

​
Register the CrowdStrike MCP server in C1

With your API client ready, register the server and provide your credentials.
1
Follow Register an MCP server and select CrowdStrike from the catalog.
2
Enter your Falcon API base URL, such as https://api.crowdstrike.com.
3
When you configure authentication, choose OAuth2 — client credentials and enter the API client’s client ID and client secret.
4
Save your changes. C1 starts a sync that discovers the tools the CrowdStrike server exposes.

​
Discover and govern tools

After you register the server, C1 runs tool discovery against CrowdStrike. Discovered tools appear on the server’s Tools tab. Each tool starts as either Pending review or automatically Approved, depending on the option chosen when the server was set up or your tenant’s default tool settings in AI > MCP > Settings. See Require tool approval and Default tool classification. Before anyone can call a CrowdStrike tool, it must be approved, added to a toolset, and bound to an access profile. Continue to Govern tools and toolsets to set this up.
Tool discovery runs even if your credentials are incorrect, so seeing discovered tools doesn’t confirm that authentication is working. You confirm your CrowdStrike credentials when an approved user successfully calls a CrowdStrike tool from their AI client.

​
Manage your CrowdStrike credentials

  • Rotate the client secret by resetting it on the API client in the Falcon console, then update the secret on the server’s authentication settings in C1.
  • Adjust access by editing the API scopes granted to the API client in CrowdStrike. See Choose API scopes.