Flightctl MCP Server

This will create a local image named `mcp-server:latest` that you can use to run the server.

Local serverstdioPython

What is the Flightctl MCP MCP server?

Flightctl MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. This will create a local image named mcp-server:latest that you can use to run the server.

What you get

  • Read-only querying of devices, fleets, events, enrollment requests, repositories, and resource syncs from Flight Control
  • Support for filtering by labels and fields using Kubernetes-style selectors
  • Context-rich JSON responses including metadata and links to related resources
  • Secure OIDC/OAuth2 refresh token–based authentication
  • Remote device console access for executing commands on managed devices
  • Automatic pagination handling for large result sets

What the assistant can call

Once Flightctl MCP is connected, these are the calls the assistant has available:

  • Logging — The server uses file-based logging to avoid conflicts with the MCP protocol on stdio: - Log Location
  • Enrollment — The Enrollment tool exposed by this server

Setting it up

quay.io/flightctl/flightctl-mcp on a container image is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need 8 environment variables: MCP_TRANSPORT, MCP_HOST, MCP_PORT, API_BASE_URL, OIDC_TOKEN_URL, OIDC_CLIENT_ID, REFRESH_TOKEN, INSECURE_SKIP_VERIFY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the cloud and infrastructure 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. Flightctl MCP's toolset — Logging, Enrollment — is a fair guide to whether it matches your workflow. It is maintained by flightctl; 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.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the flightctl mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
LoggingThe server uses file-based logging to avoid conflicts with the MCP protocol on stdio: - **Log Location**: ~/.local/share/flightctl-mcp/flightctl-mcp.log - **Log Rotation**: Automatic rotation at 10MB with 5 backup files
EnrollmentThe Enrollment tool exposed by this server.

How to install the Flightctl MCP MCP server

#### For Claude Desktop (stdio):
```json
{
  "mcpServers": {
    "flightctl": {
      "command": "python",
      "args": ["main.py"],
      "env": {
        "MCP_TRANSPORT": "stdio"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
MCP_TRANSPORTConfiguration value read at startup.Optional
MCP_HOSTEndpoint or connection string the server talks to.Optional
MCP_PORTConfiguration value read at startup.Optional
API_BASE_URLEndpoint or connection string the server talks to.Yes
OIDC_TOKEN_URLCredential the server authenticates with.Yes
OIDC_CLIENT_IDConfiguration value read at startup.Optional
REFRESH_TOKENCredential the server authenticates with.Yes
INSECURE_SKIP_VERIFYConfiguration value read at startup.Optional

Example prompts to try

  • Use Flightctl MCP to Logging.
  • Use Flightctl MCP to Enrollment.

Frequently asked questions

It connects Flightctl MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Logging, Enrollment) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Flightctl MCP directly.