Aircraft registry search, flight history, and analytics powered by ADS-B Exchange data.
Most file and storage access work still happens through a UI a human drives. FlightDB MCP server moves it into the conversation instead. Aircraft registry search, flight history, and analytics powered by ADS-B Exchange data.
Connect your AI assistant to FlightDB — aircraft registry search, flight history, and analytics via the Model Context Protocol.
The server publishes 10 tools. What each one is for:
Flight_list_flights — Paginated flights with filters: aircraft, airport, country, date rangeFlight_list_aircraft — Paginated aircraft directory with registration, country, ICAO filtersFlight_get_aircraft_from_list — Single aircraft header by idFlight_get_aircraft_detail — Full aircraft profile with all flights and aggregatesFlight_flights_by_year — Per-year flight counts for an aircraftFlight_flights_by_distance — Per-year flights binned by trip distance (Short / Medium / Long)Flight_flights_by_country — Per-year arrival-country breakdown for an aircraftFlight_airport_visits — Per-airport visit and stay aggregates by yearFlight_visit_history — Visit timeline for an aircraftFlight_get_airport — Airport details by IATA or ICAO codeSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. FlightDB's toolset — Flight_list_flights, Flight_list_aircraft, Flight_get_aircraft_from_list and 7 more — is a fair guide to whether it matches your workflow. It is maintained by flightdb; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Flight_list_flights | Paginated flights with filters: aircraft, airport, country, date range |
| Flight_list_aircraft | Paginated aircraft directory with registration, country, ICAO filters |
| Flight_get_aircraft_from_list | Single aircraft header by id |
| Flight_get_aircraft_detail | Full aircraft profile with all flights and aggregates |
| Flight_flights_by_year | Per-year flight counts for an aircraft |
| Flight_flights_by_distance | Per-year flights binned by trip distance (Short / Medium / Long) |
| Flight_flights_by_country | Per-year arrival-country breakdown for an aircraft |
| Flight_airport_visits | Per-airport visit and stay aggregates by year |
| Flight_visit_history | Visit timeline for an aircraft |
| Flight_get_airport | Airport details by IATA or ICAO code |
{
"mcpServers": {
"flightdb": {
"url": "https://flightdb.org/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.