Fleetp MCP

Created By
SimplyMinimal7 months ago
An MCP server for Fleet device management
Overview

What is Fleet MCP?

Fleet MCP is a Model Context Protocol (MCP) server designed for managing devices through Fleet Device Management, focusing on security monitoring and compliance enforcement.

How to use Fleet MCP?

To use Fleet MCP, set up the server with your Fleet instance URL and API token, and configure it for read-only or full access based on your needs. You can run it using the command: FLEET_SERVER_URL={FLEET_SERVER_URL} FLEET_API_TOKEN={FLEET_API_TOKEN} uvx fleet-mcp run.

Key features of Fleet MCP?

  • Host Management: Manage and query hosts across your fleet.
  • Live Query Execution: Execute osquery queries in real-time.
  • Policy Management: Create and monitor compliance policies.
  • Software Inventory: Track software installations and vulnerabilities.
  • Team & User Management: Organize hosts and users into teams.
  • Activity Monitoring: Audit logs and track Fleet activities.

Use cases of Fleet MCP?

  1. Managing device compliance across various operating systems.
  2. Monitoring security vulnerabilities in real-time.
  3. Executing live queries to gather data from devices.

FAQ from Fleet MCP?

  • Can Fleet MCP manage devices across different OS?

Yes! Fleet MCP supports Windows, Mac, Linux, iOS, and Android devices.

  • Is Fleet MCP open-source?

Yes! Fleet MCP is open-source software licensed under the MIT License.

  • How do I ensure secure access?

Use read-only mode for safe exploration and store sensitive tokens in configuration files.

Server Config

{
  "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"
      }
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
SimplyMinimal
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago