SimBrief MCPServer

What Emanuele94/SimBrief-MCPServer MCP server does

Emanuele94/SimBrief-MCPServer MCP server exposes sections of a SimBrief operational flight plan through the Model Context Protocol. It is intended for use with Claude Desktop and requires a free SimBrief account. The server reads the Pilot ID from SIMBRIEF_PILOT_ID, so the account identifier can be supplied in the MCP client configuration rather than added to source code.

The server includes fourteen tools. Flight summary data includes the flight number, aircraft, route, distance, cruise information, estimated en-route time, and fuel. Other tools expose weather reports, the fuel breakdown, aircraft and load weights, operational times, aircraft details, the ATC flight-plan string, the waypoint navigation log, NOTAMs, alternate-airport information, crew, performance data, and sensitivity impacts from altitude or cost-index changes. A full-flight-plan tool returns the raw JSON for custom analysis.

How it works

Each tool accepts an optional plan_id. If that value is omitted, the server fetches the account's latest dispatch. This supports both quick questions about the most recent plan and targeted inspection of a particular plan when its identifier is available.

A connected client can ask for individual sections instead of processing the entire response. For example, an agent can request only the weather, fuel plan, or first part of a navlog. The raw JSON option is available when an application needs to perform its own analysis across the complete plan.

The README describes the server as requiring no OAuth, Cloudflare handling, or additional infrastructure. Development tests mock the SimBrief API and therefore do not require internet access or a real Pilot ID, but normal use still requires a configured SimBrief account identifier.

Setup and configuration

The project requires Python 3.11 or newer and uv. Install it by cloning the repository and running uv sync from the project directory. The MCP client configuration starts the server with uv run, the project path, and server.py.

Set SIMBRIEF_PILOT_ID in the MCP configuration's env object. The Pilot ID is available in SimBrief under Account Settings. The server refuses to start when this variable is missing. After adding the configuration, restart Claude Desktop so the tools become available.

The documented client configuration targets Claude Desktop on macOS or Windows. It uses an absolute local path to the cloned project, so that path must be changed to the location on the host running the server.

Tools and capabilities

Available capabilities include:

• Reading flight number, aircraft, route, cruise, distance, ETE, and fuel
• Retrieving METAR, TAF, and ATIS for departure, arrival, and alternate airports
• Inspecting taxi, trip, contingency, alternate, reserve, and extra fuel
• Viewing operating weights and scheduled OUT, OFF, ON, and IN times
• Producing the ATC flight-plan string and aircraft equipment details
• Reviewing waypoint altitude, distance, and fuel values in the navlog
• Reading departure, arrival, and en-route NOTAMs
• Checking alternate-airport data, crew assignments, and available takeoff or landing performance
• Comparing fuel and time effects for altitude and cost-index changes
• Returning complete raw plan JSON

Limitations and notes

The server is specifically tied to SimBrief flight-plan data and does not create a general flight-planning system. Performance information is returned only when it is available in the plan. A SimBrief account and Pilot ID are required for normal operation, while the repository's offline tests use mocked API responses. The README documents Claude Desktop integration; it does not establish compatibility with other MCP clients.

Emanuele94/SimBrief-MCPServer MCP server is released under the MIT license. Its documented local workflow uses uv, Python, a cloned repository, and a configured Pilot ID rather than a published package command.