Connects AI agents to Microsoft Flight Simulator to read and write SimVars, L-vars, events, and execute RPN calculator code.
Also known as robin24/simconnect-mcp, simconnect-mcp
- Stars
- 2
- Tools
- 32
- Downloads, 30 days
- 188
- Latest version
- 1.0.2
- Last commit
- Sep 2, 2026
- License
- AGPL-3.0
What is SimConnect MCP?
SimConnect connects AI agents to Microsoft Flight Simulator to read and write SimVars, L-vars, events, and execute RPN calculator code. It exposes 32 tools, such as msfs_connect, msfs_disconnect, msfs_get_connection_status.
Summary generated from the project's README
About SimConnect MCP server
SimConnect MCP provides a bridge between AI coding agents and Microsoft Flight Simulator for add-on development. It allows developers to interact with the simulator by reading and writing SimVars, L-vars, and events. The server supports complex tasks like executing RPN calculator code and managing aircraft-specific data through native SDK support for PMDG 777 and 737 NG3 models.
This server runs locally on the same machine as the simulator and connects via stdio. Users can set it up using uvx to fetch the runtime automatically. It requires Microsoft Flight Simulator 2020 or 2024 to be running. For full L-var support, the MobiFlight WASM module should be installed in the simulator community folder. The server includes extensive built-in catalogs for variables and provides tools to search for nearby airports, load flight plans, or save flight files to automate scenario testing.
What you can do with it
- 1Develop aircraft-specific logicDevelopers can use the server to read and write local variables for complex add-ons like the Fenix A320.
- 2Interact with PMDG aircraft systemsThe server can directly access PMDG flight management computer data and control cockpit switches.
Written from the project's README. Every use case is checked against a quote from it.
How to install SimConnect MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall SimConnect MCP in Claude Code
$ claude mcp add simconnect-mcp -- uvx simconnect-mcpInstall SimConnect MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"simconnect-mcp": {
"command": "uvx",
"args": [
"simconnect-mcp"
]
}
}
}Install SimConnect MCP in VS Code
.vscode/mcp.json
{
"servers": {
"simconnect-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"simconnect-mcp"
]
}
}
}Install SimConnect MCP in VS Code CLI
$ code --add-mcp '{"name":"simconnect-mcp","type":"stdio","command":"uvx","args":["simconnect-mcp"]}'Install SimConnect MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"simconnect-mcp": {
"command": "uvx",
"args": [
"simconnect-mcp"
]
}
}
}Install SimConnect MCP in Codex
$ codex mcp add simconnect-mcp -- uvx simconnect-mcpInstall SimConnect MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.simconnect-mcp] command = "uvx" args = ["simconnect-mcp"]
Install SimConnect MCP in Gemini CLI
$ gemini mcp add -s user simconnect-mcp uvx -- simconnect-mcpInstall SimConnect MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"simconnect-mcp": {
"command": "uvx",
"args": [
"simconnect-mcp"
]
}
}
}SimConnect MCP tools 32
Detected from the READMEmsfs_connectmsfs_disconnectmsfs_get_connection_statusmsfs_get_simvarmsfs_set_simvarmsfs_get_simvars_bulkmsfs_search_simvarsmsfs_list_simvar_categoriesmsfs_watch_simvarmsfs_trigger_eventmsfs_search_eventsmsfs_trigger_custom_event
| msfs_connect | — | |
| msfs_disconnect | — | |
| msfs_get_connection_status | — | |
| msfs_get_simvar | — | |
| msfs_set_simvar | — | |
| msfs_get_simvars_bulk | — | |
| msfs_search_simvars | — | |
| msfs_list_simvar_categories | — | |
| msfs_watch_simvar | — | |
| msfs_trigger_event | — | |
| msfs_search_events | — | |
| msfs_trigger_custom_event | — |
Show all 32 toolsShow fewer tools
msfs_get_lvarmsfs_set_lvarmsfs_list_lvarsmsfs_execute_calculator_codemsfs_search_lvarsmsfs_browse_lvar_catalogmsfs_get_aircraft_snapshotmsfs_get_nearby_airportsmsfs_get_facility_infomsfs_send_sim_textmsfs_set_aircraft_positionmsfs_get_pmdg_varmsfs_get_pmdg_cdumsfs_send_pmdg_eventmsfs_search_hubhopmsfs_list_hubhop_aircraftmsfs_load_flightmsfs_save_flightmsfs_load_flight_planmsfs_create_ai_object
| msfs_get_lvar | — | |
| msfs_set_lvar | — | |
| msfs_list_lvars | — | |
| msfs_execute_calculator_code | — | |
| msfs_search_lvars | — | |
| msfs_browse_lvar_catalog | — | |
| msfs_get_aircraft_snapshot | — | |
| msfs_get_nearby_airports | — | |
| msfs_get_facility_info | — | |
| msfs_send_sim_text | — | |
| msfs_set_aircraft_position | — | |
| msfs_get_pmdg_var | — | |
| msfs_get_pmdg_cdu | — | |
| msfs_send_pmdg_event | — | |
| msfs_search_hubhop | — | |
| msfs_list_hubhop_aircraft | — | |
| msfs_load_flight | — | |
| msfs_save_flight | — | |
| msfs_load_flight_plan | — | |
| msfs_create_ai_object | — |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablerobin24/simconnect-mcp is public and reachablegithub.com/robin24/simconnect-mcp ↗Pass
- Package names this repository as its sourcesimconnect-mcp names robin24/simconnect-mcp as sourcepypi.org/project/simconnect-mcp/ ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-09-02github.com/robin24/simconnect-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from simconnect-mcpPass
- No critical advisory in the package or its dependencies31 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model32 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubSimConnect MCP Server
An MCP (Model Context Protocol) server that connects AI coding agents to Microsoft Flight Simulator via SimConnect. This server is built for add-on development — full read/write access to SimVars, L-vars, events, calculator code execution, and embedded documentation.
What It Does
- Read/write any SimVar — altitude, heading, speed, autopilot settings, engine parameters, and 1,080+ more from a comprehensive built-in catalog, with unit selection and honest failures on a rejected write
- Read/write L-vars — aircraft-specific local variables used by add-on developers (Fenix A320, FlyByWire A32NX, PMDG, etc.), including live enumeration of what the loaded aircraft has actually registered
- PMDG 777 and 737 NG3 native SDK support — direct access to all aircraft data fields and control events via the PMDG SDK Client Data Areas, plus CDU screen reading with colors/formatting
- Trigger events — toggle switches, set autopilot modes, control lights, fire custom MobiFlight events
- Execute RPN calculator code — run arbitrary Reverse Polish Notation code directly in the sim
- Search and discover variables — searchable catalogs of SimVars, events, and aircraft-specific L-vars with human-readable names and valid values
- Facilities lookup — nearby airports sorted by distance and detail lookup for a specific airport, waypoint, NDB or VOR by ICAO identifier, read directly from SimConnect's facility subscription
- Flight and scenario tools — load and save
.FLTflights, load a.PLNflight plan, and spawn an AI aircraft or object, for scripting test scenarios instead of setting them up by hand - Embedded documentation — SimConnect reference docs served as MCP resources, available offline
- Aircraft-specific catalogs — pre-built variable databases with panel groupings, display names, and value descriptions. Ships with 1,607 PMDG 777 variables (777-200LR/200F/300ER/F) and 1,861 PMDG 737 NG3 variables (-600/700/800/900 incl. BBJ/BDSF/BCF).
- HubHop integration — search the MobiFlight HubHop community preset database directly as an MCP tool, or use the built-in client to generate and extend L-var catalogs for any supported aircraft
Prerequisites
- Microsoft Flight Simulator (MSFS 2020 or 2024) running on the same machine
- uv — provides
uvx, which fetches the server and its Python runtime for you - MobiFlight WASM Module (optional, for L-var support) — install in your MSFS Community folder. Download from MobiFlight
Installation
Published on PyPI as simconnect-mcp,
and listed in the MCP Registry as
io.github.robin24/simconnect-mcp.
Once uv is installed, no separate install step is
needed — uvx fetches and runs the server on demand:
uvx simconnect-mcp
That starts the server on stdio, which is what an MCP client does for you. Run it by hand only to check that it starts; press Ctrl+C to stop.
To pin a version, use uvx simconnect-mcp@1.0.1.
From source (for development)
git clone https://github.com/robin24/simconnect-mcp.git
cd simconnect-mcp
# Creates the virtual environment and installs the dev group too
uv sync
Configuring as an MCP Server
Claude Code
Via CLI:
claude mcp add --transport stdio simconnect -- uvx simconnect-mcp
Or to make it available across all projects:
claude mcp add --transport stdio --scope user simconnect -- uvx simconnect-mcp
Via JSON (~/.claude/settings.json or project-level .claude/settings.json):
{
"mcpServers": {
"simconnect": {
"command": "uvx",
"args": ["simconnect-mcp"]
}
}
}
OpenAI Codex CLI
Via CLI:
codex mcp add simconnect -- uvx simconnect-mcp
Via JSON:
{
"mcpServers": {
"simconnect": {
"command": "uvx",
"args": ["simconnect-mcp"]
}
}
}
Gemini CLI
Via CLI:
gemini mcp add --transport stdio simconnect -- uvx simconnect-mcp
Via JSON (~/.gemini/settings.json):
{
"mcpServers": {
"simconnect": {
"command": "uvx",
"args": ["simconnect-mcp"]
}
}
}
MCP Inspector (Interactive Testing)
uv run mcp dev src/simconnect_mcp/server.py
Note: To run a local checkout instead of the published package, replace
uvx simconnect-mcpwithuv run --directory /path/to/simconnect-mcp simconnect-mcp, using the absolute path to your clone.
Tools (32)
Every tool is prefixed msfs_, carries explicit readOnlyHint/destructiveHint annotations, and returns a typed result or a structured error — never a fabricated success. The tables below are generated from the live server (name, kind, and title come straight from each tool's ToolAnnotations); descriptions are the one-line summary from the tool's own docstring:
uv run python -c "
import asyncio
from simconnect_mcp.server import mcp
async def m():
for t in sorted(await mcp.list_tools(), key=lambda x: x.name):
kind = 'read' if t.annotations.readOnlyHint else 'write'
print(f'| \`{t.name}\` | {kind} | {t.annotations.title} |')
asyncio.run(m())"
Connection (3)
| Tool | Kind | Description |
|---|---|---|
msfs_connect |
write | Establish a SimConnect connection to MSFS |
msfs_disconnect |
write | Close the SimConnect connection to MSFS |
msfs_get_connection_status |
read | Check connection state, whether the sim is running/paused |
SimVar Operations (6)
| Tool | Kind | Description |
|---|---|---|
msfs_get_simvar |
read | Read a SimVar value by name, in the requested unit |
msfs_set_simvar |
write | Write a value to a settable SimVar — fails honestly rather than reporting success on a rejected write |
msfs_get_simvars_bulk |
read | Read several SimVars in one call; one failing entry doesn't abort the rest |
msfs_search_simvars |
read | Search the SimVar catalog by keyword |
msfs_list_simvar_categories |
read | List every SimVar category with its variable count |
msfs_watch_simvar |
read | Sample a SimVar over time, returning a time series for debugging |
Units: msfs_get_simvar (and msfs_set_simvar) accept an optional unit argument and always report the unit actually used in the result. Omit unit and the bundled SimVar catalog supplies a sensible default for that variable; for a variable the catalog doesn't know, the default is "number".
Event Operations (3)
| Tool | Kind | Description |
|---|---|---|
msfs_trigger_event |
write | Fire a SimConnect event, with an optional parameter |
msfs_search_events |
read | Search SimConnect events by keyword, optionally filtered by category |
msfs_trigger_custom_event |
write | Fire a custom event as a key event through the MobiFlight WASM module |
L-Var Operations (6)
| Tool | Kind | Description |
|---|---|---|
msfs_get_lvar |
read | Read an L-var (local variable) value from the current aircraft |
msfs_set_lvar |
write | Write a value to an L-var on the current aircraft |
msfs_list_lvars |
read | Enumerate the L-vars the currently loaded aircraft has registered |
msfs_execute_calculator_code |
write | Execute RPN calculator code in the simulator |
msfs_search_lvars |
read | Search known aircraft L-vars by keyword across the bundled catalogs |
msfs_browse_lvar_catalog |
read | Browse the aircraft L-var catalogs — list catalogs, the panels in one, or the variables on one panel |
msfs_list_lvars asks the MobiFlight WASM module to enumerate what the aircraft has actually registered, live — but the module caps its reply at 1000 names and still reports the list as complete when it truncates. A busy add-on setup (GSX and similar) can crowd the aircraft's own variables out of the response entirely; watch for truncated: true. Treat the catalogs and the live listing as a starting point, not a guaranteed inventory — msfs_get_lvar reads any name you supply, whether or not it surfaced in either one.
Aircraft State (1)
| Tool | Kind | Description |
|---|---|---|
msfs_get_aircraft_snapshot |
read | Read a snapshot of the current aircraft state (position, speed, attitude, and key systems in one call) |
Facilities (2)
| Tool | Kind | Description |
|---|---|---|
msfs_get_nearby_airports |
read | List airports near a point, nearest first |
msfs_get_facility_info |
read | Look up one airport, waypoint, NDB or VOR by ICAO identifier |
Airports are world-wide (SimConnect returns the full 85,249-airport list, cached after the first collection). Waypoints, NDBs and VORs are scoped to wherever the aircraft currently is, so they are re-collected on every call rather than cached — a cached navaid list would keep answering for the aircraft's previous position after a reposition or a flight.
Utilities (2)
| Tool | Kind | Description |
|---|---|---|
msfs_send_sim_text |
write | Display a text overlay message in the simulator (debug feedback) |
msfs_set_aircraft_position |
write | Reposition the aircraft (test scenario setup) |
PMDG 777 / 737 NG3 (3)
| Tool | Kind | Description |
|---|---|---|
msfs_get_pmdg_var |
read | Read a PMDG aircraft data field by name — switches, MCP values, fuel qty, FMC data (777 or 737 NG3) |
msfs_get_pmdg_cdu |
read | Read a PMDG CDU screen as text rows with per-cell color and formatting |
msfs_send_pmdg_event |
write | Send a PMDG control event — toggle a switch, press a button, set a selector (777 or 737 NG3) |
These tools use the PMDG SDK Client Data Areas for direct binary access to the aircraft state — bypassing the MobiFlight L-var bridge. The right SDK (777 or 737 NG3) is auto-detected from the loaded aircraft, or can be forced with the variant argument. Requires EnableDataBroadcast=1 and EnableCDUBroadcast.N=1 in the aircraft's options.ini (777_Options.ini or 737NG3_Options.ini). The 777 has three CDUs (Capt/Center/F-O); the 737 NG3 has two (Capt/F-O). See PMDG 777 SDK Reference and PMDG 737 NG3 SDK Reference for details.
HubHop (2)
| Tool | Kind | Description |
|---|---|---|
msfs_search_hubhop |
read | Search the MobiFlight HubHop community preset database |
msfs_list_hubhop_aircraft |
read | List the aircraft that HubHop has presets for |
Unlike every other tool, these two reach HubHop's HTTP API rather than the simulator, so they work with MSFS closed. The first call downloads and caches the full preset database (~17 MB); later calls in the same server process are served from that in-memory cache, which both tools share and which re-fetches on its own every 6 hours. Either tool accepts refresh=true to force an immediate re-fetch.
Flight and Scenario (4)
| Tool | Kind | Description |
|---|---|---|
msfs_load_flight |
write | Load a saved flight, replacing the current one |
msfs_save_flight |
write | Save the current flight to a .FLT file — refuses to overwrite an existing file unless overwrite=true is passed explicitly |
msfs_load_flight_plan |
write | Load a .PLN flight plan into the aircraft's GPS/FMS, replacing whatever plan is currently active |
msfs_create_ai_object |
write | Spawn an AI aircraft or object at a position — reports whether SimConnect accepted the request, which is not the same as the object existing (MSFS ignores an unmatched title silently) |
These wrap the underlying SimConnect flight/scenario file operations for scripting test setups (e.g. "load this approach", "save the current state", "spawn traffic nearby") rather than driving them by hand in the sim's own UI. msfs_create_ai_object is confirmed live end-to-end — spawned, verified to answer a targeted SimVar request, then removed again — by tests/live/test_live_flight.py. msfs_save_flight was also confirmed live, including the multi-second post-save SimConnect stall documented in CLAUDE.md's Known Sim Behaviours; its own live tests were retired in the 2026-08-29 live-suite trim once that finding was captured there, since what remained (the overwrite-guard logic) is pure Python already covered by tests/test_flight.py's mocks. msfs_load_flight and msfs_load_flight_plan are mock-only by design — see tests/live/test_live_flight.py's module docstring for why. See Running the live tests below.
Variable Catalogs
The server ships with comprehensive variable catalogs for search and discovery, so that AI agents can find the right variable names without guessing.
SimVar Catalog (1,080+ variables)
The built-in SimVar catalog covers all documented MSFS simulation variables across 25 categories:
| Category | Vars | Category | Vars |
|---|---|---|---|
| Aircraft Engine | 112 | Aircraft Avionics | 122 |
| Aircraft Fuel | 48 | Miscellaneous | 162 |
| Aircraft Controls | 50 | Landing Gear | 54 |
| Autopilot | 39 | Flight Instrumentation | 45 |
| Aircraft Lights | 25 | Aircraft Position and Speed | 46 |
| Camera | 34 | Radio Navigation | 66 |
| Services | 42 | Aircraft Electrics | 47 |
| Flight Model | 11 | Aircraft Systems | 24 |
| Environment | 14 | and more... |
The catalog is sourced from both the SimConnect Python package and the official MSFS SDK documentation, ensuring complete coverage including camera controls, ground services, circuit breakers, GPS/NAV/COM radios, and flight model variables.
Aircraft L-Var Catalogs
L-var catalogs provide searchable, human-readable databases for specific aircraft add-ons. The server picks one in three steps, and tells you in the result message which step answered — the three carry very different confidence:
- Probe the PMDG SDK client data area. Authoritative, and independent of what the aircraft calls itself. This is the step that matters, because PMDG airframes do not identify themselves as PMDG: a real PMDG 737-800 reports
TITLEas737-800 PAX SSW TC, with no vendor name anywhere in it. Matching titles alone never worked for them. - Match
title_patternagainstTITLE/ATC_MODEL. The fallback, and the only mechanism available to a catalog you supply yourself. - Search every catalog and say so. Results then carry a
Catalogcolumn so you can see which aircraft each row belongs to, rather than reading another aircraft's variables as if they were yours.
Pass catalog=<key> to scope a search explicitly, or call msfs_browse_lvar_catalog with no arguments to list the available keys.
The obvious shortcut — broadening
title_patternto737— is deliberately not taken. It would match the iFly 737 MAX and Asobo's own 737 just as happily, and hand their users a PMDG catalog for an aircraft that isn't a PMDG. An honest "no catalog detected" beats a confidently wrong one.
Included catalogs:
| Aircraft | Variables | Panels | Source |
|---|---|---|---|
| PMDG 777 (all variants) | 1,607 | 28 | SDK header parse + HubHop |
| PMDG 737 NG3 (-600/700/800/900/BBJ/BDSF/BCF) | 1,861 | 27 | SDK header parse + HubHop |
Each variable includes a display name, category, writability flag, and (where applicable) a map of valid values.
No Fenix catalog ships — a prior fenix_a320.json (1,433 plain L-vars) was removed in favor of HubHop's own broader, community-maintained FenixSim coverage (2,273 presets, current the moment Fenix ships an update, where a bundled snapshot would only go stale). Search it live with msfs_search_hubhop(vendor="FenixSim"), or regenerate a local catalog file with the HubHop client below and drop it into src/simconnect_mcp/data/ — every *.json there is auto-discovered on startup, so it works immediately with no code change.
Adding New Aircraft Catalogs
The fastest way to add a new aircraft is via the built-in HubHop client:
# See what's available
python -m simconnect_mcp.data.hubhop --list-vendors
# Generate a catalog (example: FlyByWire A32NX)
python -m simconnect_mcp.data.hubhop \
--vendor "FlyByWire Simulations" \
--aircraft "A320neo" \
--aircraft-name "FlyByWire A32NX" \
--title-pattern "A32NX" \
-o fbw_a32nx.json
Or update an existing one:
python -m simconnect_mcp.data.hubhop --vendor FenixSim --merge fenix_a320.json
You can also use the Python API:
from simconnect_mcp.data.hubhop import HubHopClient
client = HubHopClient()
presets = client.fetch_presets(vendor="FlyByWire Simulations", aircraft="A320neo")
catalog = client.build_catalog(presets, aircraft="FlyByWire A32NX", title_pattern="A32NX")
client.save_catalog(catalog, "fbw_a32nx.json")
Or create catalogs manually by placing a JSON file in src/simconnect_mcp/data/. All *.json files are auto-discovered on startup. See docs/extending-catalogs.md for the full guide, JSON schema, and best practices.
Resources
| URI | Type | Content |
|---|---|---|
simconnect://docs/overview |
text/markdown |
SimConnect architecture and key concepts |
simconnect://docs/simvars/{category} |
text/markdown |
SimVar reference by category |
simconnect://docs/events/{category} |
text/markdown |
Event reference by category |
simconnect://docs/rpn |
text/markdown |
RPN calculator syntax guide |
simconnect://docs/lvars |
text/markdown |
L-var usage for add-on development |
simconnect://docs/best-practices |
text/markdown |
Common pitfalls and performance tips |
simconnect://docs/pmdg/{variant} |
text/markdown |
PMDG SDK reference; variant is 777 or 737 (a leading B is accepted, case-insensitive) |
simconnect://state/connection |
application/json |
Live connection status |
simconnect://state/aircraft |
application/json |
Current aircraft title, type, and position |
Prompts
| Prompt | Purpose |
|---|---|
debug_simvar |
Step-by-step guide for debugging a misbehaving SimVar |
analyze_aircraft_vars |
Enumerate and categorize all L-vars on current aircraft |
create_addon_boilerplate |
Generate add-on starter code by type |
rpn_helper |
Translate natural language to RPN calculator code |
simconnect_code_review |
Review SimConnect code for common issues |
Project Structure
src/simconnect_mcp/
├── server.py # FastMCP instance, lifespan, tool registration
├── connection.py # SimConnectManager singleton + native set_lvar
├── dispatch.py # SimConnectDispatcher — owns the SimConnect dispatch loop
├── simvar_access.py # SimVarAccessor — generic SimVar reads/writes via data definitions
├── facilities.py # Facility (*_LIST) message parsing and accumulation
├── pmdg.py # PMDG 777 SDK structs, CDU rendering, data manager
├── pmdg_ng3.py # PMDG 737 NG3 SDK structs, CDU rendering, data manager
├── tools/
│ ├── __init__.py # @handle_simconnect_errors, @require_connection decorators
│ ├── connection_tools.py # connect_to_sim, disconnect_from_sim, get_connection_status
│ ├── simvars.py # SimVar CRUD via SimVarAccessor (1,080+ vars in the catalog)
│ ├── events.py # Event trigger/search + built-in catalog
│ ├── lvars.py # L-var read/write/search/enumerate/browse catalogs/calculator code
│ ├── pmdg.py # PMDG tools — auto-dispatch to 777 or 737 NG3
│ ├── aircraft.py # get_aircraft_snapshot — combined state snapshot
│ ├── facilities.py # Airport/navaid lookup on top of facilities.py
│ ├── flight.py # load/save flight, load flight plan, spawn AI object
│ ├── hubhop.py # HubHop preset search, exposed as MCP tools
│ ├── utilities.py # send_sim_text, set_aircraft_position
│ ├── models.py # Shared Pydantic result/error models
│ └── formatting.py # Pagination and markdown-table helpers
├── data/
│ ├── catalog.py # L-var catalog loader and search engine
│ ├── simvar_catalog.py # SimVar catalog loader, unit resolution, string-var detection
│ ├── hubhop.py # MobiFlight HubHop API client (CLI + library), in-memory cache
│ ├── pmdg_777.json # PMDG 777 catalog (1,607 vars, 28 panels)
│ ├── pmdg_737.json # PMDG 737 NG3 catalog (1,861 vars, 27 panels)
│ └── simvars_catalog.json # Built-in SimVar catalog (1,080+ vars, 25 categories)
├── vendor/ # Byte-faithful to upstream except two documented local changes
│ ├── simconnect_mobiflight.py # unmodified
│ └── mobiflight_variable_requests.py # log-level demotion + response-channel routing
└── docs/ # Embedded documentation, served as MCP resources
├── overview.md, simvars.md, events.md, rpn.md, lvars.md, best_practices.md
├── pmdg_777.md # PMDG 777 SDK reference
└── pmdg_737.md # PMDG 737 NG3 SDK reference
The PMDG catalogs are regenerated from the SDK headers via scripts/parse_pmdg_sdk.py — it auto-detects the struct name and CDU count, so the same script handles both 777 and 737 NG3.
Development
# Run the mocked test suite (no MSFS required; live tests are deselected by default)
uv run pytest
# Run tests with verbose output
uv run pytest -v
# Run only specific test files
uv run pytest tests/test_hubhop.py # HubHop client tests
uv run pytest tests/test_simvars.py # SimVar catalog tests
# Lint
uv run ruff check src/ tests/
Tests mock SimConnect so the suite above runs without MSFS. tests/conftest.py provides a mock SimConnect with realistic SimVar values.
SimConnect MCP questions
How do I add SimConnect MCP to Claude Code?
Run claude mcp add simconnect-mcp -- uvx simconnect-mcp in your terminal. Add --scope user to make it available in every project.
How do I add SimConnect MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does SimConnect MCP provide?
It exposes 32 tools, including msfs_connect, msfs_disconnect, msfs_get_connection_status, msfs_get_simvar, msfs_set_simvar.
What software is required to run this server?
You need Microsoft Flight Simulator (MSFS 2020 or 2024) running on the same machine and the uv tool installed.
Does it support PMDG aircraft?
Yes, it provides native SDK support for PMDG 777 and 737 NG3, allowing direct access to aircraft data fields and CDU screen reading.
How do I get L-var support?
L-var support is optional and requires the MobiFlight WASM Module to be installed in your MSFS Community folder.
Can I use this to automate flight scenarios?
Yes, you can load and save .FLT flights, load .PLN flight plans, and spawn AI aircraft or objects to script test scenarios.