Skip to main content

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.

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

Module Description
Core Basic connectivity and system information
AgentWorks Call, list, and observe Charlotte AI agents and their execution traces
Case Management Case lifecycle management, evidence attachment, tagging, and templates
Cloud Security Kubernetes containers, image vulnerabilities, CSPM asset inventory, IOM findings, suppression rules, cloud risks, cloud insights, and cloud groups
Correlation Rules Search, create, update, and manage NG-SIEM correlation rules
Custom IOA Create and manage Custom IOA behavioral detection rules and rule groups
Data Security Search, create, and update Data Security classifications, policies, content patterns, applications, web locations, sensitivity labels, and file types
Detections Find, aggregate, and analyze detections to understand malicious activity
Discover Search application inventory and managed/unmanaged assets, including drive encryption and system-insights posture
Exclusions Search, create, update, and delete IOA, machine learning, sensor visibility, and certificate-based exclusions
Firewall Management Search and manage firewall rules and rule groups
Fusion SOAR Search Fusion SOAR workflow definitions and executions, read execution results, and run on-demand workflows
Guardian Monitor AI agent activity, sessions, tool usage, and inventory
Host Groups Search, create, update, and delete host groups; manage group membership
Hosts Manage and query host/device information
Identity Protection Entity investigation and identity protection analysis
Intel Research threat actors, IOCs, and intelligence reports
IOC Search, create, and remove custom indicators of compromise
NGSIEM Execute CQL queries against Next-Gen SIEM
Policies Search, create, update, and delete prevention, sensor update, firewall, device control, response, and content update policies; manage host-group assignment, enable/disable, and precedence
Quarantine Search quarantine records, preview action counts, and release, unrelease, or delete quarantined files
Real Time Response Audit, summarize, and run read-only RTR triage workflows
Recon Search and aggregate Falcon Intelligence Recon notifications (recon alerts), monitoring rules, and exposed-data records for dark web, leaked credentials, and typosquatting, and preview prospective rule noise
Scheduled Reports Manage scheduled reports and download report files
Sensor Usage Access and analyze sensor usage data
Serverless Search for vulnerabilities in serverless functions
Shield SaaS security posture, checks, alerts, and app inventory
Spotlight Manage and analyze vulnerability data and security assessments
Zero Trust Assessment Retrieve Zero Trust Assessment posture scores and sensor and OS hardening signals for hosts

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

Quick Start

Install

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

{
  "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 image
docker 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

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 registered
falcon-mcp --read-only

# Expose exactly two tools, nothing else
falcon-mcp --tools falcon_search_detections,falcon_search_hosts

# Keep the module, drop one tool
falcon-mcp --modules hostgroups --exclude-tools falcon_delete_host_groups

# All of detections, plus one tool from a module you did not enable
falcon-mcp --modules detections --tools falcon_search_applications
Flag Environment Variable Effect
--read-only FALCON_MCP_READ_ONLY Registers only read-only tools
--tools FALCON_MCP_TOOLS Allow-list of tool names, added to the enabled modules
--exclude-tools FALCON_MCP_EXCLUDE_TOOLS Deny-list of tool names

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

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 install
git clone https://github.com/CrowdStrike/falcon-mcp.git
cd falcon-mcp
uv sync --all-extras

# Run tests
uv run pytest

Developer Documentation

Registries

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

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.

Metadata

Release files for falcon-mcp 0.20.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for falcon-mcp 0.20.2
File Size Uploaded Provenance Actions
falcon_mcp-0.20.2.tar.gz 329.3 kB With provenance Details for falcon_mcp-0.20.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for falcon-mcp 0.20.2
File Interpreter ABI Platform Actions
falcon_mcp-0.20.2-py3-none-any.whl Python 3 none any Details for falcon_mcp-0.20.2-py3-none-any.whl

Total release size: 661.1 kB

Release files / falcon_mcp-0.20.2.tar.gz

Download URL falcon_mcp-0.20.2.tar.gz
Size 329.3 kB
Tags Source
SHA-256 checksum
How to use checksums
20b9dddacca8d89e78d6d1339bf6b3755039bafb41f545622981861f5fddd78c
BLAKE2b-256 checksum
How to use checksums
221d40ae28ac34da9ce65dd3be42c1844a4b8871f2c08d6c740e485ccda4b242
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.

Transparency log

Release files / falcon_mcp-0.20.2-py3-none-any.whl

Download URL falcon_mcp-0.20.2-py3-none-any.whl
Size 331.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9e1bab032ecf183ffa8830b77865a5514161173cc141a2631d3619b63c42ffa8
BLAKE2b-256 checksum
How to use checksums
a37dc6c1f938adffc5b8b50c3bc6acc919d0d6380aae01934ac2c3440bf4c19e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.

Transparency log

Security for falcon-mcp 0.20.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for falcon_mcp-0.20.2.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page