flighty-mcp
flighty-mcp is a read-only MCP server that exposes your personal Flighty app flight data for querying, analysis, and visualization.
List flights (
list_my_flights): Retrieve your flight history as geo-ready legs with departure/arrival airport coordinates, filterable by year, date range (after/before), result limit, and an upcoming-only flag. Returns up to 200 results (newest first) including flight number, airline, origin/destination city/country, lat/lon, and times.Get a specific flight (
get_flight): Fetch the most recent flight leg matching a given flight number (e.g. "UA194"), case- and space-insensitive — returns a single leg or null if not found.Aggregate stats (
flight_stats): View summary statistics over your flight history (or a specific year) — total flight count, total distance (km), unique airports and airlines, top routes by frequency, and top airlines by flight count.Animate a trip (
animate_trip): Generate a shareable flight-animator route link for a trip to a destination, resolving connected flights from your inferred home airport (or a specified origin); returns one-way and round-trip URLs and handles ambiguous destinations gracefully.
Configuration: Supports customization of the Flighty database path, user ID, and flight animator base URL. Requires macOS Full Disk Access to read the Flighty database.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@flighty-mcp list my flights from June 2025"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
flighty-mcp
A read-only MCP server that exposes your personal Flighty app flight data as geo-ready legs with departure and arrival coordinates. Query your flight history by date, year, or flight number; browse aggregate stats (distance, unique airports/airlines, top routes).
Credit: inspired by LukasHaas/flighty-mcp for the original idea.
Tools
list_my_flights
List your own flights as geo-ready legs (departure/arrival airports with coordinates).
Arguments:
year(optional): Filter to a calendar year (e.g. 2025).after(optional): Only flights departing on/after this ISO date (YYYY-MM-DD).before(optional): Only flights departing before this ISO date (YYYY-MM-DD).upcoming_only(optional): Return non-archived flights, soonest first. Full history is newest first.limit(optional): Maximum number of legs to return (default 200).
Returns: List of leg objects with this structure:
{
"date": "2025-06-23",
"flight_no": "UA194",
"airline": {
"iata": "UA",
"name": "United Airlines"
},
"from": {
"iata": "SFO",
"city": "San Francisco",
"country": "United States",
"lat": 37.6213,
"lon": -122.379
},
"to": {
"iata": "JFK",
"city": "New York",
"country": "United States",
"lat": 40.6413,
"lon": -73.7781
},
"departure": "2025-06-23T10:30:00",
"arrival": "2025-06-24T01:15:00Z"
}get_flight
Get your most recent flight leg matching a flight number (e.g. "UA194").
Arguments:
flight_no: The flight number (case- and space-insensitive).
Returns: A single leg object (or null if no match found).
flight_stats
Aggregate stats over your flights: counts, distance, unique airports/airlines, and top routes.
Arguments:
year(optional): Filter stats to a calendar year. Omit for all-time.
Returns: Stats object with this structure:
{
"flights": 42,
"distance_km": 18500.5,
"unique_airports": 15,
"unique_airlines": 5,
"top_routes": [
{ "route": "SFO -> JFK", "count": 8 },
{ "route": "JFK -> SFO", "count": 7 }
],
"top_airlines": [
{ "iata": "UA", "name": "United Airlines", "count": 12 }
],
"year": "all_time"
}animate_trip
Build a flight-animator route link for your trip to a place.
Resolves the connected flights from your home (or origin) to destination and returns shareable links: url (one-way trip) and round_trip_url (there and back). May instead return a resolution prompt with status ambiguous_destination, confirm_home, or no_match.
Arguments:
destination: Where the trip goes — IATA code, city, or country (e.g. "Japan", "NRT").origin(optional): Starting location — IATA code, city, or country. Defaults to your inferred home (most common departure airport).after(optional): ISO date (YYYY-MM-DD); only trips departing on/after it.before(optional): ISO date (YYYY-MM-DD); only trips departing before it.
Example: "animate my flight to Japan"
Returns: If successful, a dict with keys status (always "ok"), url, round_trip_url (if a return is found), home, destination, stops (summary), start_date, end_date, leg_count, and home_confidence. On ambiguity or mismatch, returns status with one of: no_match (no flights match criteria), ambiguous_destination (multiple cities match the destination), or confirm_home (inferred home confidence is low—returns top alternatives for confirmation).
Route link format: the ?d= value is base64url of {"v":1,"stops":[…]} (the versioned envelope shared with flight-animator's decoder). Each stop carries code, lat, lon, label, and optional arrive/depart (ISO 8601). We always embed lat/lon so the animator needs no airport-table lookup and so points outside its bundled dataset still render — consumers should prefer the embedded coordinates over resolving the code.
Related MCP server: flightaware-mcp
Installation
Install uv, clone this repository,
and replace /absolute/path/to/flighty-mcp below with the clone's absolute path.
Codex
codex mcp add flighty -- uv --directory /absolute/path/to/flighty-mcp run flighty-mcpRestart Codex after adding the server. The ChatGPT desktop app, Codex CLI, and Codex IDE extension share this configuration.
Claude Code
claude mcp add --scope user flighty -- uv --directory /absolute/path/to/flighty-mcp run flighty-mcpClaude Desktop and Cursor
Add this entry to Claude Desktop's claude_desktop_config.json or Cursor's
~/.cursor/mcp.json:
{
"mcpServers": {
"flighty": {
"command": "uv",
"args": ["--directory", "/absolute/path/to/flighty-mcp", "run", "flighty-mcp"]
}
}
}Restart the client after saving the file.
VS Code / GitHub Copilot
Add this to your user or workspace mcp.json:
{
"servers": {
"flighty": {
"type": "stdio",
"command": "uv",
"args": ["--directory", "/absolute/path/to/flighty-mcp", "run", "flighty-mcp"]
}
}
}You can open the user file with MCP: Open User Configuration from the Command Palette.
Other stdio MCP clients
Use the mcpServers JSON example above, or adapt its command and args values to your
client's configuration format. This server uses standard MCP over stdio and has no
client-specific runtime behavior.
Configuration
Variable | Default | Description |
|
| Path to the Flighty app's SQLite database. |
| Auto-detected from | The Flighty user ID to query (normally auto-detected; set only if overriding). |
|
| Base URL for |
Full Disk Access Requirement
Important: The MCP server needs macOS Full Disk Access to read the Flighty database.
Symptom: If the server fails to connect or reads hang indefinitely, it's likely because Full Disk Access is missing.
Solution:
Open System Preferences → Privacy & Security → Full Disk Access.
Add the app that will launch this server:
For Codex, Claude Desktop, Cursor, or VS Code, add that application.
For Claude Code or another terminal-launched client, add Terminal (or your terminal app).
Restart the app (or kill and relaunch it).
Try again.
The database lives at ~/Library/Containers/com.flightyapp.flighty/Data/Documents/, which is in your user's private container — Full Disk Access is required for any application to read it.
Available Tools
3 toolsflight_statsA
Aggregate stats over your flights: counts, distance, unique airports/airlines, top routes.
Args: year: Filter stats to a calendar year. Omit for all-time. upcoming_only: If true, return only upcoming (non-archived) flights. Default false returns your full flight history.
Inputs: year, upcoming_only.
get_flightA
Get your most recent flight leg matching a flight number (e.g. "UA194").
Args: flight_no: The flight number (case- and space-insensitive).
Inputs: flight_no (required). Returns: result
list_my_flightsA
List your own flights as geo-ready legs (departure/arrival airports with coordinates).
Args: year: Filter to a calendar year (e.g. 2025). after: Only flights departing on/after this ISO date (YYYY-MM-DD). before: Only flights departing before this ISO date (YYYY-MM-DD). upcoming_only: If true, return only upcoming (non-archived) flights. Default false returns your full flight history. limit: Maximum number of legs to return (default 200, newest first).
Inputs: year, after, before, upcoming_only, +1 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clear, distinct purpose: aggregate stats, get a specific flight by number, and list flights with filters. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (flight_stats, get_flight, list_my_flights), making them predictable and readable.
With only 3 tools, the server feels slightly undersized for a flight tracking domain, but each tool serves a core read operation. The count is reasonable for a minimal API.
The server is read-only, missing any create, update, or delete operations for flights. Users cannot add or modify flight data, which is a significant gap for a personal flight tracker.
Maintenance
Related MCP Connectors
Geo-based flight search MCP server. Find more flights between any two places on earth
Flight search MCP server providing search, pagination, and itinerary details for AI assistants.
Search and compare flight offers through a cache-aware Streamable HTTP MCP server for AI agents.
Unofficial FlightStats MCP — wraps the Cirium FlightStats Flex API (api.flightstats.com/flex)
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides access to a trip tracking SQLite database. This server enables AI assistants to query and manage flight trip information including users, airports, and flight details.Apache 2.0
- AlicenseAqualityAmaintenanceMCP server for FlightAware AeroAPI that enables live flight tracking, airport boards, operator and aircraft lookup, schedule retrieval, and flight alert management via natural language.34641 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes SQLite datasets as queryable tools and resources via Streamable HTTP, enabling read-only exploration and SQL queries.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server that exposes Garmin Connect health data from a local SQLite database to AI assistants, enabling queries for recent days, sleep, weekly trends, and a guarded SQL query surface.MIT