Set up the CrowdStrike Falcon MCP server (Remote)
Connect the MCP server that CrowdStrike runs to Mintive (formerly MintMCP) so your team can investigate detections, hosts, policies, and threat intelligence through their own Falcon accounts. Each member signs in to Falcon once, the tools they get follow their Falcon roles, and Falcon's audit log records every call under their user. Mintive brokers the OAuth flow and logs every tool call. For the Mintive-hosted connector, which authenticates with a Falcon API client, see Set up the CrowdStrike Falcon MCP server (Hosted).
Prerequisites
- A Mintive admin account
- A Falcon Administrator to create the MCP client
- A Falcon CID in US-1, US-2, or EU-1. CrowdStrike doesn't offer this server in GovCloud.
- For each member who connects, one of these Falcon roles in the CID:
| Role | Access |
|---|---|
| CrowdStrike MCP User | Tools allowed by the member's other Falcon roles, including write tools |
| CrowdStrike MCP User - Read Only | Read-only tools allowed by the member's other Falcon roles |
| Falcon Administrator | All available tools |
Create an MCP client in Falcon
CrowdStrike's server doesn't support dynamic client registration, and Mintive isn't on CrowdStrike's list of pre-approved clients, so a Falcon Administrator registers Mintive as an MCP client once per CID.
-
In the Falcon console, go to Support and resources > Resources and tools > Client Management, then open the MCP clients tab.
-
Click Create MCP Client.
-
Enter a Client name, such as
Mintive. -
In Redirect URI, enter the callback for your Mintive region:
Mintive region Redirect URI US https://app.mintmcp.com/oauth/callbackEU https://eu.mintmcp.com/oauth/callbackFalcon compares the URI exactly, including the path, so don't add a trailing slash.
-
Keep Confidential selected as the client type. Falcon doesn't let you change the type after creation.
-
Click Create.
-
Copy the Client ID and Client secret. The secret is shown only once. If you lose it, reset the secret on the MCP client to generate a new one.
Assign MCP roles
- In the Falcon console, open user management and select the member.
- Add CrowdStrike MCP User or CrowdStrike MCP User - Read Only, as described in Prerequisites.
- Save the user.
The MCP role decides whether a member can authorize Mintive and whether they get write tools. Their other Falcon roles decide which tools they see.
Add the server to Mintive
The Mintive catalog lists one CrowdStrike Falcon (Remote) entry per Falcon cloud, with the server URL, OAuth, and per-user credentials already set. You supply the client ID and secret from the MCP client.
| Falcon cloud | Catalog entry | MCP server URL |
|---|---|---|
| US-1 | CrowdStrike Falcon (Remote) - US-1 | https://mcp.crowdstrike.com/v1 |
| US-2 | CrowdStrike Falcon (Remote) - US-2 | https://mcp.us-2.crowdstrike.com/v1 |
| EU-1 | CrowdStrike Falcon (Remote) - EU-1 | https://mcp.eu-1.crowdstrike.com/v1 |
- In Mintive, go to MCP store > Manage store.
- Find the entry for your Falcon cloud in the catalog and click Install.
- Expand OAuth Client Advanced Settings and paste the Client ID and Client Secret from the MCP client. Leave Override OAuth endpoints unticked, so Mintive reads CrowdStrike's OAuth endpoints from the server.
- Click Install.
Connect and authorize
Each member connects once:
- In Mintive, open the CrowdStrike Falcon (Remote) MCP you installed and click Connect.
- Sign in to Falcon.
- On the Authorize Application screen, select the CID and click Accept.
A member without an MCP role in any CID sees an error screen after signing in instead of the consent screen.
Verify the connection
The MCP's Tools tab lists two tools: search_tools, which finds Falcon tools by keyword, and execute_tool, which runs one by name. Agents call search_tools first, then execute_tool with the tool name it returns.
Try a prompt such as:
- "Search Falcon detections from the last 7 days and summarize them by severity."
Control which Falcon tools agents can run
Tool customization only sees search_tools and execute_tool, so turning off execute_tool turns off every Falcon action. To allow some Falcon tools and block others, create a tool arguments rule that matches the Falcon tool name in the name argument of execute_tool. For example, this rule blocks Falcon write tools and lets read tools through:
| Field | Value |
|---|---|
| Tool pattern | execute_tool$ |
| Argument condition | name: ^falcon_(delete|remove|update|create|perform|set|add|manage)_ |
| Action | Block |
A new or changed rule can take up to a minute to apply.
The Falcon MCP roles are the other control: CrowdStrike MCP User - Read Only removes write tools for that member in Falcon itself.
Token lifetime
- A member's access token lasts 12 hours. After it expires, the member authorizes again. Agents that run on a schedule stop working until the member reconnects.
- Deleting the MCP client in Falcon blocks new authorizations, but tokens already issued stay valid until they expire, up to 12 hours.
Security considerations
- Authentication: Every request runs as the member's own Falcon user through the OAuth 2.1 authorization code flow with PKCE.
- Authorization: Falcon limits each member to the tools their MCP role and other Falcon roles allow. Mintive rules add a second layer on top.
- Audit trail: Mintive logs each tool call against the member. In Falcon, search the console for audit and open Falcon UI audit logs. Each call appears as MCP Request > Tool Call (User) with the member as analyst, the Falcon tool name, and the MCP client ID. The consent appears as Accept access delegation.
- Client secret: Falcon shows it only once, so store it in a secrets manager.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
invalid client_id at sign-in | The client ID is wrong, or the MCP Server URL points at a different Falcon cloud than the CID that holds the MCP client. |
redirect_uri mismatch | The MCP client's redirect URI doesn't match your Mintive region's callback exactly. |
| Error screen after signing in to Falcon | The member has no CrowdStrike MCP role in any CID. Assign one under Assign MCP roles. |
A Falcon tool doesn't appear in search_tools | The member's Falcon roles don't allow it, or the CID isn't licensed for that module. |
| Calls fail with an auth error after working | The 12-hour token expired. Reconnect in Mintive. |
Next steps
- Set up the CrowdStrike Falcon MCP server (Hosted): Use a Falcon API client, shared credentials, or GovCloud
- Agent Monitor rules: Block or allow specific Falcon tools
- Tool customization: Control which tools reach your members