# MCP FLIGHT SERVER

flightclaw runs as a Model Context Protocol server, giving any MCP-compatible client tools to search Google Flights, track price history, and alert on price drops. No API key required — pricing comes directly from Google Flights.

Compatible with: Claude Code, Claude Desktop, Cursor, Cline, Continue, and any client that speaks MCP.

# install

Claude Code

# add the MCP server claude mcp add flightclaw -- python3 server.py

click to copy · clone jackculpan/flightclaw first, then run from that directory

Claude Desktop

# add to claude_desktop_config.json { "mcpServers": { "flightclaw": { "command": "python3", "args": ["/path/to/flightclaw/server.py"] } } }

click to copy · restart Claude Desktop after editing

Dependencies

# requires python 3.10+ pip install flights "mcp[cli]"

click to copy

~~~

# tools exposed

search_flights — find flights for a route & date, filter by cabin, stops, airline, time

search_dates — find cheapest dates across a date range (calendar view)

track_flight — add a route to the watch list with optional target price

check_prices — refresh prices for all tracked routes, return drops

list_tracked — show all tracked routes with current vs starting price

remove_tracked — stop tracking a route

Filters supported in search_flights: passengers (adults / children / infants), airline, max price, max duration, departure window, arrival window, layover length, sort order (price / duration / stops).

~~~

# example prompts

"find nonstop flights LHR to JFK in july, business class"
"track BA 117 LHR to JFK on july 1, alert me under $400"
"what's the cheapest day to fly london to new york this summer?"
"check all my tracked flights for price drops"
"search flights with no more than one stop, departing before 10am"

~~~

# why an MCP server

Flight search APIs are expensive and rate-limited. flightclaw piggybacks on Google Flights via the open-source fli library, so your agent can search at zero marginal cost. Prices come back in your local currency (auto-detected by IP).

Tracked routes persist locally as JSON, so price history stays on your machine — no cloud account, no telemetry, no third-party data sharing.

copied to clipboard