An MCP server that provides tools for managing and monitoring your Fleet Device Management instance.
Connect Fleet to Claude, Cursor or any other MCP client and it stops being a tab you switch to. An MCP server that provides tools for managing and monitoring your Fleet Device Management instance. The fleet mcp server is what makes that connection.
A Model Context Protocol (MCP) server that enables AI assistants to interact with Fleet Device Management for device management, security monitoring, and compliance enforcement.
fleet-mcp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Prerequisites — 1. Install uv (recommended) or pip: bash # Install uv (recommended) curl -LsSf https://astral.sh/uv/install.sh | shConfiguration — Go to: Settings → Cursor Settings → MCP → Add new global MCP serverSystem — Write/Modify Tools (Requires readonly=false)Configuration is passed through the environment: FLEET_SERVER_URL, FLEET_API_TOKEN, FLEET_READONLY, FLEET_ALLOW_SELECT_QUERIES, YOUR_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Before configuring any MCP client, ensure you have: 1. Install uv (recommended) or pip: 2. Fleet API Token: Generate an API token from your Fleet instance: Option 1) - Log into Fleet UI - Navigate to: My account → Get API token - Copy the token for use in configuration Option 2) - Create an API-Only user with fleetctl > Note: This API token and your fleet instance URL
Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Fleet's toolset — Prerequisites, Configuration, System — is a fair guide to whether it matches your workflow. It is maintained by SimplyMinimal; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Prerequisites | 1. **Install uv** (recommended) or pip: bash # Install uv (recommended) curl -LsSf https://astral.sh/uv/install.sh | sh |
| Configuration | Go to: Settings → Cursor Settings → MCP → Add new global MCP server |
| System | <details> <summary><b>Write/Modify Tools (Requires <code>readonly=false</code>)</b></summary> |
{
"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"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
Before configuring any MCP client, ensure you have: 1. Install uv (recommended) or pip: 2. Fleet API Token: Generate an API token from your Fleet instance: Option 1) - Log into Fleet UI - Navigate to: My account → Get API token - Copy the token for use in configuration Option 2) - Create an API-Only user with fleetctl > Note: This API token and your fleet instance URL
| Variable | Description | Required |
|---|---|---|
| FLEET_SERVER_URL | Endpoint or connection string the server talks to. | Yes |
| FLEET_API_TOKEN | Credential the server authenticates with. | Yes |
| FLEET_READONLY | Configuration value read at startup. | Optional |
| FLEET_ALLOW_SELECT_QUERIES | Configuration value read at startup. | Optional |
| YOUR_TOKEN | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.