fleet

Fleet MCP exposes a set of tools that let an AI assistant interact with a Fleet Device Management instance. Through the MCP server, you can query host information, run real-time osquery queries against managed hosts, and manage policies and compliance monitoring. The server also provides capabilities for software inventory, vulnerability tracking, and fleet-level activities/audit logging with optional read-only mode to ensure safety. With the provided configuration, you can connect via your preferred MCP client (for example Claude Desktop, Cursor, Cline, Continue, Zed, Windsurf, etc.) and use the Fleet MCP tools to perform tasks like listing hosts, executing queries, inspecting installed software, and validating policy compliance across your fleet.

Prerequisites:

• A Fleet instance with API access token permissions
• Python and/or uv installed on your machine (recommended: install uv)
• Access to the internet to pull the fleet-mcp package

Installation steps:

1. Install uv (recommended, as shown in the docs): curl -LsSf https://astral.sh/uv/install.sh | sh

2. Install the fleet-mcp package (via uv) and run the MCP server: uv install fleet-mcp # if using uv to manage packages uvx fleet-mcp run

3. Create or edit your MCP client configuration to point at your Fleet MCP server: { "mcpServers": { "fleet": { "command": "uvx", "args": ["fleet-mcp", "run"], "env": { "FLEET_SERVER_URL": "https://your-fleet-instance.com", "FLEET_API_TOKEN": "your-api-token", "FLEET_READONLY": "true", "FLEET_ALLOW_SELECT_QUERIES": "true" } } } }

4. Run the MCP client configuration with your environment variables in place and ensure the Fleet API token and server URL are correctly set.

Tips and considerations:

• Use the read-only mode (FLEET_READONLY true) for safe experimentation; enable SELECT queries with FLEET_ALLOW_SELECT_QUERIES if you need to run read-only SQL queries.
• Keep API tokens secure; consider using a config file or environment management to avoid embedding tokens in plain text.
• If your client requires a different launcher (e.g., global install), replace the command or adjust the path to fleet-mcp accordingly.
• Ensure network access from the MCP runner to your Fleet instance and that the API token has appropriate permissions for the requested actions.
• The MCP supports multiple clients; reuse the same fleet server configuration across Claude Desktop, Cursor, Cline, Continue, Zed, Windsurf, etc.