fsaircraft.net

MCP server

Point Claude, ChatGPT, Cursor or your own agent at one URL and it can search 5,655 Microsoft Flight Simulator add-ons, compare what 7 stores charge for the same title, and check whether today's price has ever been beaten. Read-only, no key, no sign-up.

https://mcp.fsaircraft.net/mcp

Transport: streamable HTTP (POST), stateless. Last price check: 2026-09-22T13:20:30.485Z (UTC). Health: /healthz.

Connect

Claude Code

claude mcp add --transport http fsaircraft https://mcp.fsaircraft.net/mcp

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL above. Or edit claude_desktop_config.json directly:

{
  "mcpServers": {
    "fsaircraft": {
      "type": "http",
      "url": "https://mcp.fsaircraft.net/mcp"
    }
  }
}

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "fsaircraft": {
      "url": "https://mcp.fsaircraft.net/mcp"
    }
  }
}

ChatGPT

Settings → Connectors → Advanced → Developer mode, then add the URL above. The search and fetch tools deep research expects are both present.

Anything else

It is plain JSON-RPC over HTTP:

curl -sS -X POST https://mcp.fsaircraft.net/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{
        "name":"search_addons",
        "arguments":{"q":"a320","sim":"msfs2024","max_price_eur":60,"limit":5}}}'

Tools

All read-only and annotated as such, all returning structured output alongside a readable summary, and all carrying as_of so an assistant can date what it quotes.

search_addons
Search the catalog. Filters: text, category, simulator, store, max price in EUR, on-sale only.
get_addon
Everything about one add-on: description, compatibility, every offer, lowest price ever, aircraft types and airports.
list_deals
What is discounted right now, deepest first, optionally only sales ending within N days.
compare_prices
Every store offer for one add-on, cheapest first, with the VAT split and an outbound link.
price_history
Daily cheapest recorded price over up to 365 days, with min, max and "is this the lowest ever".
list_stores
Which storefronts we track, how much of each catalog is discounted, and whether prices include VAT.
list_developers
Studios in the catalog, busiest first.
find_aircraft_type
Resolve "737 MAX" or "Cessna 172" to an ICAO Doc 8643 designator.
list_addons_for_aircraft
Every studio’s version of one real-world aircraft type, cheapest first.
list_sceneries_for_airport
Every scenery we carry for one airport, by ICAO or IATA code.
search / fetch
OpenAI-shaped aliases, required by ChatGPT deep-research and company-knowledge connectors.

Two resources come with them — fsaircraft://llms.txt (what this catalog is and how to read it) and fsaircraft://addon/{slug} — plus the prompts deal_digest and find_cheapest.

Try asking

  • "Cheapest way to get an A320 for MSFS 2024 under €60?"
  • "What's on sale for European airport scenery under €15 right now?"
  • "Has the Fenix A320 ever been cheaper than it is today?"
  • "Which studios make a 737-800, and what do they cost?"
  • "Build me a €100 starter pack: one airliner and two German airports."

Questions people ask

Do I need an API key?
No. The server is anonymous and read-only — it exposes the same public catalog the website shows. There are no write tools, so nothing an assistant does here can change anything.
How fresh are the prices?
Every tool result carries an as_of timestamp: the moment our scrapers last read the stores. Prices are re-checked daily, not fetched live when you ask. Last check: 2026-09-22T13:20:30.485Z (UTC).
What counts as a discount?
The current price is below the highest price we have ever recorded for that same offer at that same store. It is never derived from a store-printed list price, so a permanent "50% off" markdown is not a deal here.
Why does an add-on show no MSFS 2024 support?
Because the store selling it has not declared any. Compatibility is taken verbatim from the store page and never inferred — "not declared" is not the same as "incompatible", and the tools are worded so an assistant repeats that distinction rather than flattening it.
Can I use this in a product?
Yes, with attribution. Facts — titles, prices, discounts, store and developer names, declared compatibility — can be reused and cited freely with a link to the fsaircraft.net page the fact came from. Product images and store-written descriptions belong to their vendors.

Prefer plain HTTP?

The same catalog is a key-less JSON API, with an OpenAPI 3.1 spec and an llms.txt. Building something on this? [email protected].