Log inSubmit server
Fleet MCP logo

Fleet MCP

Connects AI assistants to Fleet Device Management for host, software, vulnerability, policy, query, and team data.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Fleet MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "fleet-mcp": {
      "command": "uvx",
      "args": [
        "fleet-mcp"
      ],
      "env": {
        "FLEET_SERVER_URL": "YOUR_VALUE_HERE",
        "FLEET_API_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

uvx fleet-mcp

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 23d ago.

Overview

The fleet-mcp MCP server connects AI assistants to a Fleet Device Management instance through its API. It exposes tools for finding hosts, reviewing activities and MDM data, inspecting software and vulnerabilities, checking policy results, and retrieving team information. Configure the server with a Fleet URL and API token, then use it from an MCP client such as Claude Desktop, Cursor, or VS Code. Reach for it when an agent needs Fleet inventory, compliance, or device-management context.

Use cases

  • Investigate a host by hostname, UUID, serial number, or IP
  • Review endpoint MDM, certificates, activities, and encryption data
  • Check software inventory and known vulnerabilities across devices
  • Inspect compliance results for Fleet policies
  • Retrieve team membership and enrollment secrets

Key features

  • Host filtering, pagination, search, and detail retrieval
  • MDM, certificate, activity, and device-mapping lookups
  • Software inventory and vulnerability queries
  • Saved query and policy result access
  • Fleet team, user, and enrollment-secret access
  • Optional read-only and SELECT-query settings

Tools80

What Fleet MCP lets your agent do. Expand a tool for its parameters.

Self-reported~1.2k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

20/23 checks healthy over the last 90d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · fleet-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
Last commit8mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed80Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Fleet MCP works

What fleet-mcp does

The fleet-mcp MCP server gives an AI assistant access to information managed by Fleet Device Management. It is suited to device inventory, endpoint investigation, software tracking, vulnerability review, compliance checks, and team administration. The available operations are centered on listing, searching, and retrieving Fleet records rather than presenting a separate local data store.

Host tools can list devices with filters, pagination, and search, or retrieve a host by ID, hostname, UUID, hardware serial, or IP-related search criteria. Host-specific lookups cover upcoming and past activities, MDM information, certificates, macadmins data, device mappings, and disk-encryption recovery keys.

How it works

The server runs as an MCP process and uses a Fleet server URL plus an API token to access the configured Fleet instance. A client starts it with the fleet-mcp run command; the example configuration uses uvx to launch the package. The assistant can then call individual Fleet tools and receive the corresponding records or reports.

Setup and configuration

Install uv or install the package with pip, then add the server to an MCP client configuration. Set FLEET_SERVER_URL to the Fleet instance URL and FLEET_API_TOKEN to a token generated in Fleet. The documented examples also set FLEET_READONLY and FLEET_ALLOW_SELECT_QUERIES.

Configuration examples are provided for Claude Desktop, Cursor, Cline, Continue, Zed, Windsurf, and VS Code. The examples use stdio with uvx fleet-mcp run. The token can be obtained from the Fleet UI or by creating an API-only user with fleetctl.

Tools and capabilities

The fleet-mcp MCP server exposes tools for:

  • Listing and searching hosts, then retrieving detailed host records.
  • Reviewing host activities, MDM data, certificates, macadmins data, mappings, and encryption keys.
  • Listing saved queries and policies, retrieving query details, and reading scheduled-query reports.
  • Listing software, retrieving software details, checking host installations, searching software, and reading installation results.
  • Listing software titles and retrieving individual title details.
  • Listing vulnerabilities and retrieving information for a specific CVE.
  • Listing teams, retrieving team details, listing team users, and reading team enrollment secrets.

Limitations and notes

The material documents Fleet access through an API token, so the token's Fleet permissions affect what the assistant can retrieve. Read-only mode and SELECT-query permission are configurable safeguards. The listed tools describe retrieval and search operations; they do not document create or update operations for policies, hosts, teams, or software.

The README includes client-specific configuration examples, but it does not document a remote HTTP deployment mode. Keep Fleet credentials in the client configuration or another protected configuration mechanism rather than exposing them in prompts.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Fleet MCP

fleet-mcp is an MCP server that connects AI assistants to Fleet Device Management and exposes tools for hosts, activities, MDM, certificates, software, vulnerabilities, policies, queries, teams, users, and team enrollment secrets, including listing, searching, and retrieving detailed records.

Install it with uv or pip, then configure an MCP client to run `uvx fleet-mcp run`.

Yes, fleet-mcp has a documented Cursor configuration. Add it through Cursor's MCP settings or its global or project `mcp.json`, using `uvx fleet-mcp run` and the Fleet URL and API token environment variables.

It can retrieve host, activity, MDM, certificate, software, vulnerability, policy, saved-query, team, user, and enrollment-secret data. Host searches support identifiers such as hostnames, UUIDs, serial numbers, and IP addresses.

Related MCP servers

All in Monitoring All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewFleet MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/fleet-mcp?style=directory)](https://allmcps.com/mcp/fleet-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/fleet-mcp"><img src="https://allmcps.com/api/badge/fleet-mcp?style=directory" alt="Fleet MCP on AllMCPs" /></a>