flighty-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLIGHTY_DB_PATH | No | Path to the Flighty app's SQLite database. | $HOME/Library/Containers/com.flightyapp.flighty/Data/Documents/MainFlightyDatabase.db |
| FLIGHTY_USER_ID | No | The Flighty user ID to query (normally auto-detected; set only if overriding). | Auto-detected from UserProfile table |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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). |
| 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). |
| flight_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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.