CrowdStrike Falcon MCP Server

[CrowdStrike Logo (Light)] [CrowdStrike Logo (Dark)]

falcon-mcp

[PyPI version] [PyPI - Python Version] [License: MIT] [MCP Registry] [GitHub MCP] [Gemini CLI Extension]

falcon-mcp is a Model Context Protocol (MCP) server that connects AI agents with the CrowdStrike Falcon platform, powering intelligent security analysis in your agentic workflows. It delivers programmatic access to essential security capabilities—including detections, threat intelligence, and host management—establishing the foundation for advanced security operations and automation.

[!IMPORTANT] falcon-mcp is now in maintenance mode. Development continues in CrowdStrike MCP, CrowdStrike's hosted MCP server, and we recommend moving to it. falcon-mcp stays supported and will keep getting security fixes, but new features will only ship in CrowdStrike MCP. See Moving to CrowdStrike MCP for what this means for you.

Documentation

Full docs are available at developer.crowdstrike.com/falcon-mcp.

Moving to CrowdStrike MCP

falcon-mcp started as an open source project to work out how AI agents should use Falcon. A lot of what we built here, including fixes and ideas from your issues and pull requests, carries forward into CrowdStrike MCP. CrowdStrike MCP is a CrowdStrike product rather than an open source project, so new development won't happen in this repository. Thanks to everyone who filed issues and sent pull requests.

For most teams, CrowdStrike MCP is the better choice now:

• It runs inside the Falcon platform, so there's nothing to install, host, or upgrade.
• Most tools keep the same falcon_* names, so prompts and agent instructions written for falcon-mcp carry over.
• Tool access follows the Falcon roles and permissions you already manage, and activity is recorded in the Falcon audit log.
• New tools and improvements ship there.

What happens to falcon-mcp:

• The same CrowdStrike team that builds CrowdStrike MCP maintains it, and it's supported through the same channels.
• Existing installs keep working. Future releases carry security and dependency fixes only.
• We're no longer accepting feature requests or feature pull requests.
• CrowdStrike MCP is available in US-1, US-2, and EU-1. If your tenant is in another cloud, or you depend on a tool that only falcon-mcp has (see Differences from CrowdStrike MCP), keep using falcon-mcp for now.
• We'll announce an end-of-life date here before the repository is archived.

Modules

See the Module Overview for required API scopes, available tools, and FQL resources.

[!NOTE] The Guardian module reads the /aidr API, whose route and parameter surface is not yet uniform across Falcon deployments. Some tools return HTTP 400 or 404 where an older surface is live. See the Guardian module docs for the details.

Quick Start

Install

Using uv (recommended)

uv tool install falcon-mcp

Using pip

pip install falcon-mcp

Configure

Set the required environment variables (or use a .env file — see the Configuration Guide):

export FALCON_CLIENT_ID="your-client-id"export FALCON_CLIENT_SECRET="your-client-secret"export FALCON_BASE_URL="https://api.crowdstrike.com"

Run

falcon-mcp

See the Getting Started guide for full installation and configuration details.

Editor Integration

Using uvx (recommended)

{  "mcpServers": {    "falcon-mcp": {      "command": "uvx",      "args": [        "--env-file",        "/path/to/.env",        "falcon-mcp"      ]    }  }}

With Module Selection

{  "mcpServers": {    "falcon-mcp": {      "command": "uvx",      "args": [        "--env-file",        "/path/to/.env",        "falcon-mcp",        "--modules",        "detections,hosts,intel"      ]    }  }}

Docker

{  "mcpServers": {    "falcon-mcp-docker": {      "command": "docker",      "args": [        "run",        "-i",        "--rm",        "--env-file",        "/full/path/to/.env",        "quay.io/crowdstrike/falcon-mcp:latest"      ]    }  }}

See the Usage guide for all command line options, module configuration, and library usage.

Container Usage

# Pull the latest imagedocker pull quay.io/crowdstrike/falcon-mcp:latest
# Run with .env file (stdio transport)docker run -i --rm --env-file /path/to/.env quay.io/crowdstrike/falcon-mcp:latest
# Run with streamable-http transport (add --api-key when the port is reachable beyond localhost)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

[!CAUTION] HTTP transports have no authentication by default. Binding to a non-loopback address (--host 0.0.0.0) exposes an unauthenticated server that anyone who can reach the port can drive with your CrowdStrike credentials. Keep the default loopback bind for local use and set --api-key whenever you bind wider. Managed runtimes such as AWS Bedrock AgentCore and Google Cloud Run sit behind their own network security layer, so this does not apply to them. See the Configuration guide.

See the Docker Deployment guide for building locally, custom ports, and advanced configurations.

Dynamic Mode

Running many modules at once inflates the context window every AI client must hold. Dynamic mode replaces the full tool surface with three tools — falcon_list_enabled_tools to see every tool the server has available, falcon_search_tools to find candidate tools by keyword and then fetch the parameter schema for the one you pick, and falcon_execute_tool to run it — so agents only load the schemas they actually need.

falcon-mcp --dynamic# or: FALCON_MCP_DYNAMIC=true

See the Dynamic Mode guide for the full discover → execute workflow and trade-offs.

Restricting What a Server Can Do

--modules is all-or-nothing per module: enabling one to get its search tools also exposes every mutating tool it carries. Three tool-level options narrow that surface.

# Investigation-only server: no tool that mutates tenant state is registeredfalcon-mcp --read-only
# Expose exactly two tools, nothing elsefalcon-mcp --tools falcon_search_detections,falcon_search_hosts
# Keep the module, drop one toolfalcon-mcp --modules hostgroups --exclude-tools falcon_delete_host_groups
# All of detections, plus one tool from a module you did not enablefalcon-mcp --modules detections --tools falcon_search_applications

Tool names are the falcon_-prefixed names your client displays. An unrecognized name aborts startup rather than being ignored, so a typo in a deny-list cannot silently leave a tool exposed.

Composing the options

--tools is additive, not a narrowing filter. It grants individual tools on top of whatever --modules already enabled, reaching across the module boundary:

• --tools X on its own registers only X — no modules are loaded by default.
• --modules detections --tools X registers every detections tool plus X, even when X belongs to a module that is not enabled. That module contributes only X, not its whole surface, and falcon_list_enabled_modules does not list it. falcon_list_enabled_tools does list X — it reports the tools available on the server, so it is the reliable answer to "is this capability available here?"

To subtract, use --exclude-tools or --read-only. All four knobs compose, and they resolve in a fixed order:

1. --exclude-tools removes a tool unconditionally, even if --tools names it.
2. --read-only removes every mutating tool unconditionally, even if --tools names it.
3. --tools adds the tools it names, bypassing the module gate.
4. --modules decides which tools are candidates by default.

Because the first two rules always win, --read-only and --exclude-tools are safe to set as a deployment-wide floor: an additive --tools list cannot widen past them. Combining them is how you express "search everything, change nothing, and don't even offer that one tool":

falcon-mcp --read-only --exclude-tools falcon_execute_rtr_read_only_command

Filtering applies to dynamic mode too — a withheld tool is absent from falcon_search_tools results and rejected by falcon_execute_tool. Because dynamic mode dispatches by name rather than registering tools individually, that rejection spells out that the tool exists but the server's configuration withholds it, and names the one rule responsible, so an agent reports a disabled tool as disabled instead of telling the user the capability does not exist. falcon_list_enabled_tools carries a filters_active field in either mode whenever a rule is in effect. The startup log reports which rules are active and how many tools --read-only and --exclude-tools withheld, so you can confirm what you deployed. Run with --debug to see the withheld tools by name.

These options filter tools, not resources. A withheld tool's FQL guide resource stays available — guides are static field documentation carrying no tenant data.

Deployment Options

• Amazon Bedrock AgentCore
• Google Cloud (Agent Platform / Gemini Enterprise)

Contributing

falcon-mcp is in maintenance mode and no longer accepts new features or modules. We still review security and dependency fixes. To report a vulnerability, follow the security policy.

# Clone and installgit clone https://github.com/CrowdStrike/falcon-mcp.gitcd falcon-mcpuv sync --all-extras
# Run testsuv run pytest

[!IMPORTANT] This project uses Conventional Commits for automated releases. Please follow the commit message format outlined in our Contributing Guide.

Developer Documentation

• Documentation Guide: Architecture and maintenance guide for the documentation
• Module Development Guide: Instructions for implementing new modules
• Resource Development Guide: Instructions for implementing resources
• Integration Testing Guide: Guide for running integration tests with real API calls

Registries

falcon-mcp is published to public MCP catalogs for discovery and one-click setup in compatible clients:

• MCP Registry
• GitHub MCP Registry
• Gemini CLI Extensions

License

This project is licensed under the MIT License - see the LICENSE file for details.

Support

falcon-mcp is maintained by the CrowdStrike team that builds CrowdStrike MCP and is supported through the same channels. It's in maintenance mode, so fixes are limited to security and dependency issues.

For more information, please see our SUPPORT file.