Flight History and Aircraft routes

FlightDB (flightdb) - URL: https://flightdb.org - What it does: Aircraft registration directory and historical flight records — search by registration, route…

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Flight List Flights: Paginated flight rows with optional filters: aircraft id substring, departure/arrival airport or city substring, country substrings, date range, sortBy (Flight scalar field), sort
  • Flight List Aircraft: Paginated aircraft directory (AircraftList): optional reg (hyphens stripped), 2-letter country, ICAO/id substring, usedBy substring, sortBy (AircraftList scalar), sortOrder. Retu
  • Flight Get Aircraft From List: Single AircraftList row by id (fast header lookup). Returns null if missing. Use get_aircraft_detail for charts and full derived stats.

What data it sees

Do you need an account

No: the server works without sign-in

FlightDB (flightdb)

  • URL: https://flightdb.org
  • What it does: Aircraft registration directory and historical flight records — search by registration, route, airport; aircraft-centric analytics (flights by year, distance buckets, destination countries, airport visits, stay duration).
  • Public features:
    • Flight and aircraft search, /flight/directory
    • Aircraft detail: /flight/[aircraftId]
    • Airport browse: /airport, /airport/[code]
  • MCP: https://flightdb.org/mcp — tools such as Flight_list_aircraft, Flight_get_aircraft_detail, Flight_list_flights, Flight_flights_by_year, Flight_flights_by_distance, Flight_flights_by_country, Flight_airport_visits, Flight_visit_history, Flight_get_airport
  • Data models: AircraftList, Aircraft, Flight, Airport

How to connect

How to connect Flight History and Aircraft routes to Claude

The server address to paste into Claude settings:

https://flight-history--flightdb.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Flight History and Aircraft routes to ChatGPT

The server address to paste into ChatGPT settings:

https://flight-history--flightdb.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Flight History and Aircraft routes to Cursor

The server address to paste into Cursor settings:

https://flight-history--flightdb.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (11)

Raw names from tools/list. Only developers need these.

Flight_list_flightsPaginated flight rows with optional filters: aircraft id substring, departure/arrival airport or city substring, country substrings, date range, sortBy (Flight scalar field), sortOrder. Returns { data, total }. Each row includes nested departure/arrival airport { id, name, municipality, timezone }.
Flight_list_aircraftPaginated aircraft directory (AircraftList): optional reg (hyphens stripped), 2-letter country, ICAO/id substring, usedBy substring, sortBy (AircraftList scalar), sortOrder. Returns { data, total }.
Flight_get_aircraft_from_listSingle AircraftList row by id (fast header lookup). Returns null if missing. Use get_aircraft_detail for charts and full derived stats.
Flight_get_aircraft_detailAll flights for an aircraft plus derived aggregates used on the detail page: flights (newest first), byYear, byDistance, byCountry, airportVisits, visitHistory. Empty aggregates when no flights.
Flight_flights_for_aircraftChronological flights for one aircraft id (same ordering as detail charts source). Lighter than get_aircraft_detail when you only need the raw flight list. Each row includes nested departure/arrival airport { id, name, municipality, timezone }.
Flight_flights_by_yearPer-calendar-year flight counts for one aircraft id ({ years, counts }).
Flight_flights_by_distancePer-year counts binned by trip distance category (Short / Medium / Long / Unknown) for one aircraft id.
Flight_flights_by_countryPer-year arrival-country flight counts for one aircraft id (stacked-series style payload).
Flight_airport_visitsPer-airport visit and stay aggregates by year for one aircraft id.
Flight_visit_historyVisit timeline / history structure for one aircraft id (same shape as UI visit history).
Flight_get_airportAirport row by IATA/ICAO code (id). Returns null if not found.