FlightDB

What FlightDB MCP server does

The FlightDB MCP server exposes FlightDB’s aircraft and flight data through the Model Context Protocol. FlightDB combines ADS-B Exchange data with official aircraft registry records, allowing an AI assistant to search aircraft, inspect flight history, and retrieve aggregate activity by year.

The service supports both broad searches and aircraft-specific analysis. An agent can filter flights by aircraft, airport, country, or date range; find aircraft by registration, country, or ICAO identifier; and look up an airport with an IATA or ICAO code. Aircraft detail responses include the profile, associated flights, and aggregate information.

How it works

Clients connect to the hosted endpoint at https://flightdb.org/mcp using Streamable HTTP. Authentication uses Google OAuth. After signing in when prompted, the client can call the available MCP tools through the remote service.

FlightDB’s underlying information comes from ADS-B Exchange and official aircraft registry records. The available analytics are organized around aircraft, flights, airports, years, countries, trip-distance categories, and airport visits. Pagination is available for the flight and aircraft listing operations.

Setup and configuration

In Claude, add a custom connector from the connector settings, name it FlightDB, and enter:

https://flightdb.org/mcp

Save the connector and complete Google sign-in when requested.

For Cursor or another MCP client that accepts a remote URL, add an entry similar to:

{
  "mcpServers": {
    "flightdb": {
      "url": "https://flightdb.org/mcp"
    }
  }
}

No local executable or environment variables are specified in the provided setup instructions. The connection uses the hosted endpoint and Google OAuth rather than a locally configured API key.

Tools and capabilities

The FlightDB MCP server provides tools for:

• Listing paginated flights with aircraft, airport, country, and date-range filters.
• Listing aircraft with registration, country, and ICAO filters.
• Retrieving a single aircraft header or a full aircraft profile with flights and aggregates.
• Counting an aircraft’s flights by year.
• Grouping yearly flights into short, medium, and long distance ranges.
• Breaking down an aircraft’s yearly arrivals by country.
• Summarizing airport visits and stays by year.
• Showing an aircraft’s visit timeline.
• Looking up airport details by IATA or ICAO code.

These operations support questions such as how many flights an aircraft made in a given year, which airports it visited most often, and which countries it reached.

Limitations and notes

FlightDB’s records are based on ADS-B Exchange and official registry data, so results should be interpreted within the coverage and characteristics of those sources. Listing operations are paginated, meaning an agent may need to request additional pages for a complete result set.