Skip to main content
A leather falconry glove resting on a wooden perch, drawn in dots

CrowdStrike Falcon MCP: setup, tools, and limits

CrowdStrike has two MCP servers: open-source falcon-mcp, now in maintenance mode, and hosted CrowdStrike MCP. Setup, API scopes, tools, and limits.

Guide
Updated 11 min read

Summary

CrowdStrike publishes two official MCP servers: falcon-mcp, an open-source Python server you run yourself with a Falcon API client, and CrowdStrike MCP, a hosted server inside the Falcon platform that falcon-mcp's maintainers now recommend. As of November 2026, falcon-mcp (version 0.20.2) is in maintenance mode with security and dependency fixes only, while CrowdStrike MCP runs in the US-1, US-2, and EU-1 clouds with tool access set by Falcon roles and every call in the Falcon audit log. Both include write tools, so access needs scoping, but falcon-mcp's documented tools stop short of containing a host, and each server sees only Falcon data.

Latest falcon-mcp release on PyPI, as of November 2026
0.20.2
Falcon clouds with hosted CrowdStrike MCP (US-1, US-2, EU-1)
3 clouds
Hosted CrowdStrike MCP access token lifetime, per a third-party guide
12 hours

Key takeaways

  1. New tools ship only in hosted CrowdStrike MCP, which serves US-1, US-2, and EU-1; falcon-mcp covers other clouds and the Fusion SOAR and Zero Trust Assessment tools the hosted server lacks.
  2. Give falcon-mcp its own API client with only the scopes for the modules you load, and run it with --read-only until you've decided which writes an agent may make.
  3. Keep falcon-mcp on stdio or the loopback address; if you expose HTTP, always set --api-key, because HTTP transports have no authentication by default.
  4. Assign the CrowdStrike MCP User - Read Only role to anyone who doesn't need write tools on the hosted server.
  5. Plan for scheduled agents on the hosted server, since a member's token reportedly expires after 12 hours and has to be re-authorized.

The short version

"CrowdStrike MCP" now means two things. falcon-mcp is the open-source server CrowdStrike released in 2025: a Python package you install, point at a Falcon API client, and run next to your AI client. CrowdStrike MCP is the hosted successor that runs inside the Falcon platform. The falcon-mcp README points most teams to the hosted server, and falcon-mcp has moved to maintenance mode.

Both cover detections, hosts, intelligence, Next-Gen SIEM queries, cases, policies, and more, and both include write tools. The hosted server runs inside Falcon, uses Falcon roles, and logs calls to the Falcon audit log. It serves three Falcon clouds, its documentation sits behind a Falcon sign-in, and the documented response actions stop short of containment. For an agent working a Falcon detection, that means it can read and update the detection but not contain the host, and it has to get identity, email, and log evidence somewhere else.

Limits for investigation work

Both servers give an agent access to Falcon under Falcon's own permissions. The limits show up when an agent tries to work an investigation from alert to close:

  • Response stops short of containment. The documented Hosts tools search, read, and tag hosts; none contains one. RTR runs read-only commands only. Writes include detections, cases, IOCs, policies, exclusions, and quarantined files. An agent that confirms a compromised laptop still has to hand containment to a person in the Falcon console. Cotool's response page shows the other arrangement: an Endpoint Alert Responder agent, triggered by a webhook on CrowdStrike Falcon detections, holds a CrowdStrike "Take Action on Hosts" tool, and its prompt has it prepare network quarantine for approval rather than isolate on its own.
  • Hosted availability. CrowdStrike MCP serves US-1, US-2, and EU-1 only, and Mintive's guide says it isn't offered in GovCloud. Tenants elsewhere are on falcon-mcp, which gets no new features.
  • Hidden documentation and pricing. The hosted server's docs sit behind a Falcon sign-in, and CrowdStrike's public pages don't publish what it costs or which subscriptions include it, so you can't size it before talking to CrowdStrike.
  • Scheduled work. Mintive reports hosted tokens last 12 hours, after which "agents that run on a schedule stop working until the member reconnects." An agent meant to pick up detections overnight stops when the token does. In Cotool, an integration is authenticated once for the organization, with OAuth or an API key, and agents start from webhook, cron, or email triggers rather than from a member's chat session.
  • Self-hosted means self-secured. falcon-mcp is pre-1.0, runs as one API identity, and leaves HTTP authentication to you.
  • One vendor's data. Either server sees Falcon. Correlating with a SIEM, identity provider, or ticketing system means adding more servers, such as the Splunk MCP server, and the quality varies widely across the official security MCP servers. An agent working the detection ends up switching between servers with different auth models and limits.

There's also a product next door. CrowdStrike sells Charlotte AI inside Falcon, describes its Agent Collaboration framework as making Falcon "the operating center of the agentic ecosystem," and announced in September 2026 that Charlotte AI AgentWorks agents can be put to work directly from Claude. falcon-mcp's AgentWorks module calls those agents. How Charlotte AI compares with other built-in assistants and with cross-stack AI SOC platforms is covered in built-in security AI vs AI SOC platforms.

Two official servers

falcon-mcpCrowdStrike MCP
PublisherCrowdStrike, MIT-licensed open sourceCrowdStrike product
Status, as of November 2026Maintenance mode; security and dependency fixes onlyWhere new tools ship
Where it runsYour machine or your container (stdio by default)Inside the Falcon platform
AuthenticationFalcon API client ID and secretOAuth sign-in as the Falcon user
AvailabilityAny Falcon cloud you set in FALCON_BASE_URLUS-1, US-2, and EU-1
How clients call toolsEach falcon_* tool registered up frontsearch_tools, then execute_tool

falcon-mcp started as an open-source project; CrowdStrike announced it in preview through Amazon Bedrock AgentCore in July 2025. Version 0.20.2 was released on PyPI on November 3, 2026, and needs Python 3.11 or later. The README says future releases carry security and dependency fixes only, feature requests are closed, and an end-of-life date will be announced before the repository is archived.

CrowdStrike MCP runs inside Falcon, so there is nothing to install, host, or upgrade. Most tools keep their falcon_* names, tool access follows the Falcon roles you already manage, and activity goes to the Falcon audit log. CrowdStrike's own documentation for it requires a Falcon sign-in. A setup guide from Mintive, a third-party MCP gateway, fills in some detail: endpoints at https://mcp.crowdstrike.com/v1, https://mcp.us-2.crowdstrike.com/v1, and https://mcp.eu-1.crowdstrike.com/v1; no GovCloud; OAuth 2.1 with PKCE; no dynamic client registration; and access tokens that last 12 hours.

Access: API scopes and Falcon roles

falcon-mcp authenticates with a Falcon API client, and each module needs specific scopes. The quick start says to enable at least Hosts: READ and Alerts: READ. Write scopes unlock mutating tools: Alerts: WRITE lets falcon_update_detections change status, assignment, comments, and tags, and Hosts: WRITE lets falcon_manage_host_grouping_tags edit tags. The NGSIEM module needs NGSIEM: READ and NGSIEM: WRITE because queries run through the asynchronous search job API.

On the hosted server, per Mintive's guide, each user needs one of three Falcon roles. CrowdStrike MCP User grants the tools the user's other roles allow, including writes. CrowdStrike MCP User - Read Only limits them to read tools. Falcon Administrator gets every available tool. A tool also won't appear if the CID isn't licensed for its module.

The modules and tools

The falcon-mcp README lists 28 modules plus Core. The ones an investigation leans on most:

  • Detections: falcon_search_detections, falcon_get_detection_details, falcon_aggregate_detections, and falcon_update_detections, across endpoint, identity, cloud, and other Falcon alert sources.
  • Hosts: falcon_search_hosts, falcon_get_host_details, and falcon_manage_host_grouping_tags.
  • NGSIEM: falcon_search_ngsiem runs CQL against Next-Gen SIEM.
  • Intel, Identity Protection, and Spotlight: threat actors, IOCs, reports, identity entities and timelines, and vulnerabilities.
  • Real Time Response: search and audit RTR sessions, open a session, and run read-only commands (ls, ps, cat, filehash, reg).
  • Case Management, IOC, Exclusions, Policies, Host Groups, Firewall, Quarantine, and Custom IOA: create, update, and delete operations on the matching Falcon objects.
  • AgentWorks: call, list, and observe Charlotte AI agents and their execution traces.

The hosted server differs slightly. CrowdStrike says Fusion SOAR and Zero Trust Assessment exist only in falcon-mcp, a Guardian tool and a Discover tool are missing from the hosted server, and Policies uses six per-type tool variants instead of one unified set.

Running every module inflates the tool list each client has to hold in context. falcon-mcp's dynamic mode, in public preview, replaces the full surface with three tools: falcon_list_enabled_tools, falcon_search_tools, and falcon_execute_tool.

Step by step

This walkthrough sets up falcon-mcp, because its setup is public. For the hosted server, a Falcon Administrator creates an MCP client under Support and resources, Resources and tools, Client Management, MCP clients, and users sign in through the OAuth flow; follow CrowdStrike's documentation in the Falcon console for client-specific steps. The broader pattern for wiring several tools into one client is in connecting security tools to Claude Code.

  1. Create an API client. In the Falcon console, go to Support, API Clients and Keys, and add a client named for the server. Grant only the scopes for the modules you plan to load. Save the client ID, secret, and base URL.
  2. Install. Use uv, which CrowdStrike recommends, or pip:
uv tool install falcon-mcp
  1. Store credentials in a .env file outside any repository:
FALCON_CLIENT_ID=your-client-id
FALCON_CLIENT_SECRET=your-client-secret
FALCON_BASE_URL=https://api.crowdstrike.com
  1. Connect your client. For Claude Code, register it as a stdio server; everything after -- is the command Claude Code runs:
claude mcp add --transport stdio falcon-mcp -- uvx --env-file /path/to/.env falcon-mcp --read-only

For Claude Desktop, add CrowdStrike's configuration to claude_desktop_config.json, limiting the modules it loads, and restart the app. For Cursor, the same JSON goes in ~/.cursor/mcp.json (or .cursor/mcp.json for one project); how Cursor's MCP approvals and admin controls differ from Claude Code's is covered in Claude Code vs Cursor for security:

{
  "mcpServers": {
    "falcon-mcp": {
      "command": "uvx",
      "args": [
        "--env-file",
        "/path/to/.env",
        "falcon-mcp",
        "--modules",
        "detections,hosts,intel"
      ]
    }
  }
}
  1. Verify. Ask the assistant to "Check connectivity to the Falcon API"; the server calls falcon_check_connectivity.
  2. Narrow the surface. --modules is all-or-nothing per module, so a module's search tools bring its mutating tools with them. Add --read-only to drop every tool that changes tenant state, or --tools and --exclude-tools for exact lists.

If several people need one shared server, CrowdStrike documents running the container over streamable HTTP. Bind beyond localhost only with an API key, which clients send as the x-api-key header:

docker run --rm -p 8000:8000 --env-file /path/to/.env \
  quay.io/crowdstrike/falcon-mcp:latest \
  --transport streamable-http --host 0.0.0.0 --api-key your-secret-key

To run either server under a triage agent instead of a desktop client, register it as one tool in an agent platform. In Cotool, a custom MCP server sits next to the built-in integrations; tool permissions can mark Falcon's write tools as needing approval in the app or Slack, and one click makes the agent read-only.

Common mistakes

  • Exposing HTTP without a key. falcon-mcp's HTTP transports have no authentication by default. Binding to 0.0.0.0 without --api-key logs a warning but still starts, and anyone who can reach the port can drive the server with your CrowdStrike credentials.
  • One over-scoped API client for everyone. falcon-mcp calls Falcon as the API client, not as the person asking. Every user of a shared server gets the client's full scopes, and Falcon sees one identity.
  • Assuming --modules limits writes. Loading the Detections module to search also loads falcon_update_detections. Use --read-only or --exclude-tools.
  • Leaving out -i in Docker. The default stdio transport needs docker run -i.
  • Trusting stale counts. CrowdStrike's quick start still says to expect 16 modules, while the README lists many more. Check the module list the server reports.
  • Expecting Guardian tools to work everywhere. CrowdStrike notes the Guardian module's /aidr API isn't uniform across Falcon deployments, so some tools return HTTP 400 or 404.
  • Starting new work on falcon-mcp by default. If your tenant is in a supported cloud, new tools will only ship in the hosted server.

Where an agent platform fits

An investigation that starts with a Falcon detection usually needs identity, email, cloud, and log evidence before anyone can close it. Agent platforms such as Cotool's AI SOC work across over 100 built-in integrations plus custom MCP and CLI tools, including your own MCP server, so CrowdStrike's server becomes one tool among several. Cotool's agents close or escalate alerts with the evidence attached, and state-changing actions can require approval in the app or Slack.

Take a Falcon detection for a suspicious binary reading browser cookies and the Keychain on a Mac. Through either CrowdStrike server, an agent can pull the detection details, the host record, and the process list from a read-only RTR session. Whether the user's identity shows a matching sign-in, and whether cloud credentials were touched, sit outside Falcon. Cotool's response page traces this case through its Endpoint Alert Responder, which splits the work across investigator subagents: the endpoint investigator finds that MeetingNotes.app read the Keychain and cookies and then ran curl, the identity investigator finds a Workspace session from a new ASN and a failed Okta MFA, and the cloud investigator finds service-account keys enumerated but none used. A reviewer subagent confirms the verdict, the detection is escalated with that evidence attached, and containment waits for an analyst to approve it.

Checklist

  • Tenant cloud confirmed: US-1, US-2, or EU-1 for hosted CrowdStrike MCP, otherwise falcon-mcp
  • Hosted: MCP client created by a Falcon Administrator; users assigned CrowdStrike MCP User or the Read Only role
  • Self-hosted: dedicated API client with only the scopes for loaded modules
  • Credentials in a .env file outside source control
  • --modules limited to what agents need, plus --read-only until writes are approved
  • HTTP transport off, or bound with --api-key and network restrictions
  • Connectivity checked with falcon_check_connectivity
  • Falcon audit log, or your own logging for falcon-mcp, reviewed for MCP activity
  • A plan for containment and other response actions the servers don't expose, such as an approval-gated host action run from an agent platform
  • A watch on the falcon-mcp README for the end-of-life date

FAQ

Does CrowdStrike have an official MCP server?
CrowdStrike has two official MCP servers. falcon-mcp is an MIT-licensed open-source server on GitHub and PyPI that you run yourself, and CrowdStrike MCP is a hosted server that runs inside the Falcon platform. The falcon-mcp README points most teams to CrowdStrike MCP and says new features ship only there.
Is falcon-mcp deprecated?
falcon-mcp is in maintenance mode rather than deprecated. Existing installs keep working and CrowdStrike still ships security and dependency fixes, but it no longer accepts feature requests, and CrowdStrike says it will announce an end-of-life date before archiving the repository. Teams outside US-1, US-2, and EU-1, or teams that need Fusion SOAR or Zero Trust Assessment tools, are told to keep using falcon-mcp for now.
Can the CrowdStrike MCP server contain a host?
The CrowdStrike MCP server documentation for falcon-mcp lists no host containment tool: the Hosts module searches hosts, reads host details, and manages grouping tags. Its Real Time Response tools run only read-only commands such as ls, ps, cat, filehash, and reg, and do not expose admin or remediation commands. It can, however, update detections, cases, IOCs, policies, exclusions, and quarantined files when the matching write scopes are granted.
Which API scopes does falcon-mcp need?
falcon-mcp needs the API scopes of each module you load; CrowdStrike's quick start says to enable at least Hosts: READ and Alerts: READ. Write scopes such as Alerts: WRITE or Hosts: WRITE unlock that module's mutating tools, and the NGSIEM module needs both NGSIEM: READ and NGSIEM: WRITE just to run a query. The Module Overview lists the scopes for every module.

Sources

  1. CrowdStrike/falcon-mcp on GitHub · accessed November 16, 2026
  2. falcon-mcp on PyPI · accessed November 16, 2026
  3. Falcon MCP - CrowdStrike Developer Center · accessed November 16, 2026
  4. Falcon MCP Module Overview · accessed November 16, 2026
  5. Falcon MCP configuration · accessed November 16, 2026
  6. Falcon MCP quick start · accessed November 16, 2026
  7. Falcon MCP editor integration · accessed November 16, 2026
  8. Falcon MCP dynamic mode · accessed November 16, 2026
  9. Falcon MCP CLI · accessed November 16, 2026
  10. Falcon MCP Hosts module · accessed November 16, 2026
  11. Falcon MCP Detections module · accessed November 16, 2026
  12. Falcon MCP NGSIEM module · accessed November 16, 2026
  13. Falcon MCP Real Time Response module · accessed November 16, 2026
  14. Set up the CrowdStrike Falcon remote MCP server (Mintive) · accessed November 16, 2026
  15. CrowdStrike brings agentic AI security workflow integrations to AWS Marketplace · accessed November 16, 2026
  16. CrowdStrike brings the Falcon platform to the Anthropic Claude Marketplace · accessed November 16, 2026
  17. Charlotte AI: Agentic Analyst for Cybersecurity · accessed November 16, 2026
  18. CrowdStrike Falcon platform evolves to lead the agentic security era · accessed November 16, 2026
  19. Connect Claude Code to tools via MCP · accessed November 16, 2026
  20. Connect to local MCP servers - Model Context Protocol · accessed November 16, 2026
  21. Model Context Protocol (MCP) - Cursor Docs · accessed November 16, 2026
  22. AI SOC Without the Black Box - Cotool · accessed November 16, 2026
  23. AI Alert Triage and Incident Response Agents - Cotool · accessed November 16, 2026
  24. Tools and Integrations - Cotool Documentation · accessed November 16, 2026
  25. Triggering Agents - Cotool Documentation · accessed November 16, 2026

Keep reading

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo