loading…
Search for a command to run...
loading…
Access your SimBrief flight plans. 14 tools covering flight summary, weather (METAR/TAF/ATIS), fuel plan, weights, times, ATC flight plan, navlog, NOTAMs, alter
Access your SimBrief flight plans. 14 tools covering flight summary, weather (METAR/TAF/ATIS), fuel plan, weights, times, ATC flight plan, navlog, NOTAMs, alternate airport, crew and performance sensitivity analysis.
A Model Context Protocol server that gives Claude Desktop direct access to your SimBrief flight plans — no Cloudflare, no OAuth, no infrastructure required.
14 tools covering every section of a SimBrief OFP:
| Tool | Description |
|---|---|
get_flight_summary |
Flight number, aircraft, route, distance, cruise, ETE, fuel |
get_weather |
METAR, TAF and ATIS for departure, arrival and alternate |
get_fuel_plan |
Full fuel breakdown: taxi, trip, contingency, alternate, reserve, extra |
get_weights |
OEW, payload, ZFW, TOW, ramp weight, landing weight |
get_times |
Scheduled OUT/OFF/ON/IN, ETE, block time, taxi, endurance |
get_atc_flightplan |
ATC flight plan string ready for filing |
get_aircraft_info |
Type, registration, engines, equipment codes |
get_navlog |
Full waypoint list with altitude, distance and fuel per leg |
get_notams |
All NOTAMs (departure, arrival, en-route) |
get_alternate_info |
Alternate airport details and navlog |
get_performance |
Takeoff & landing performance (TLR), if available |
get_crew |
Captain, first officer, dispatcher, purser, flight attendants |
get_impacts |
Fuel and time sensitivity to altitude and cost index changes |
get_full_flight_plan |
Complete raw JSON for custom analysis |
All tools accept an optional plan_id parameter — leave it empty to always fetch your latest dispatch.
git clone https://github.com/Emanuele94/SimBrief-MCPServer.git
cd SimBrief-MCPServer
uv sync
Your SimBrief Pilot ID is passed via an environment variable in the MCP config — no code changes needed.
Find your Pilot ID under SimBrief → Account Settings → Pilot ID.
Add the following to your claude_desktop_config.json:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"simbrief": {
"command": "uv",
"args": [
"run",
"--project", "/absolute/path/to/SimBrief-MCPServer",
"python",
"/absolute/path/to/SimBrief-MCPServer/server.py"
],
"env": {
"SIMBRIEF_PILOT_ID": "your_pilot_id_here"
}
}
}
}
Then restart Claude Desktop. The SimBrief tools will appear automatically.
The server will refuse to start with a clear error message if
SIMBRIEF_PILOT_IDis not set.
Once connected, you can ask Claude things like:
Install dev dependencies:
uv sync --all-extras
Run tests:
uv run pytest -v
Lint and format:
uv run ruff check .
uv run ruff format .
All tests run fully offline — the SimBrief API is mocked so no internet connection or real Pilot ID is required.
git checkout -b feature/my-feature)uv run pytest && uv run ruff check .)mainPRs must pass all checks (tests + lint) before they can be merged.
MIT
Добавь это в claude_desktop_config.json и перезапусти Claude Desktop.
{
"mcpServers": {
"emanuele94-simbrief-mcpserver": {
"command": "npx",
"args": []
}
}
}PRs, issues, code search, CI status
Database, auth and storage
Reference / test server with prompts, resources, and tools.
Secure file operations with configurable access controls.