SimBrief MCPServer

SimBrief MCP Server

A Model Context Protocol server that gives Claude Desktop direct access to your SimBrief flight plans — no Cloudflare, no OAuth, no infrastructure required.

Features

14 tools covering every section of a SimBrief OFP:

All tools accept an optional plan_id parameter — leave it empty to always fetch your latest dispatch.

Requirements

• Python 3.11+
• uv
• A SimBrief account (free)

Installation

git clone https://github.com/Emanuele94/SimBrief-MCPServer.git
cd SimBrief-MCPServer
uv sync

Configuration

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.

Claude Desktop integration

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_ID is not set.

Usage examples

Once connected, you can ask Claude things like:

• "What's my latest flight plan?"
• "Show me the weather for my next flight."
• "How much fuel do I have planned and what's the breakdown?"
• "Give me the full ATC flight plan string."
• "What happens to fuel burn if I fly 2000 ft lower?"
• "Show me the first 20 waypoints of my navlog."

Development

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.

Contributing

1. Fork the repository
2. Create a feature branch (git checkout -b feature/my-feature)
3. Make your changes and add tests
4. Ensure the CI pipeline passes locally (uv run pytest && uv run ruff check .)
5. Open a Pull Request against main

PRs must pass all checks (tests + lint) before they can be merged.

License

MIT