Google Flights MCP server, CLI, and Python library for searching flights, flexible travel dates, airports, and booking options through a reverse engineered Google Flights API workflow.
Fli is not an official Google project; upstream describes reverse engineered Google Flights API access., Flight availability, fares, booking options, baggage fees, cabin details, and vendor links can change quickly and must be verified on the airline or booking provider before purchase., The search client impersonates browser-like requests, rate limits calls, and retries failures; excessive automated searches may be blocked or violate service expectations., The MCP server returns booking links but does not buy tickets, spend money, or manage reservations., Travel results should not be treated as legal, immigration, visa, safety, or airline-policy advice.
Privacy notes
Search queries can reveal travel plans, home or work locations, dates, passenger counts, cabin preferences, airline preferences, alliances, budgets, and destination interests., Requests and returned results may be visible to Google Flights, MCP client logs, model providers, and local process logs., Booking URLs and vendor options can contain itinerary parameters that should not be shared publicly when travel plans are sensitive., Avoid entering passport data, loyalty account credentials, payment details, traveler names, or private booking confirmations into prompts.
Author
punitarani
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, network access, third-party handling.
4 areas
SafetyGeneralFli is not an official Google project; upstream describes reverse engineered Google Flights API access.
SafetyThird-party handlingFlight availability, fares, booking options, baggage fees, cabin details, and vendor links can change quickly and must be verified on the airline or booking provider before purchase.
SafetyNetwork accessThe search client impersonates browser-like requests, rate limits calls, and retries failures; excessive automated searches may be blocked or violate service expectations.
SafetyGeneralThe MCP server returns booking links but does not buy tickets, spend money, or manage reservations.
SafetyGeneralTravel results should not be treated as legal, immigration, visa, safety, or airline-policy advice.
PrivacyGeneralSearch queries can reveal travel plans, home or work locations, dates, passenger counts, cabin preferences, airline preferences, alliances, budgets, and destination interests.
PrivacyNetwork accessRequests and returned results may be visible to Google Flights, MCP client logs, model providers, and local process logs.
PrivacyThird-party handlingBooking URLs and vendor options can contain itinerary parameters that should not be shared publicly when travel plans are sensitive.
PrivacyCredentials & tokensAvoid entering passport data, loyalty account credentials, payment details, traveler names, or private booking confirmations into prompts.
Safety notes
Fli is not an official Google project; upstream describes reverse engineered Google Flights API access.
Flight availability, fares, booking options, baggage fees, cabin details, and vendor links can change quickly and must be verified on the airline or booking provider before purchase.
The search client impersonates browser-like requests, rate limits calls, and retries failures; excessive automated searches may be blocked or violate service expectations.
The MCP server returns booking links but does not buy tickets, spend money, or manage reservations.
Travel results should not be treated as legal, immigration, visa, safety, or airline-policy advice.
Privacy notes
Search queries can reveal travel plans, home or work locations, dates, passenger counts, cabin preferences, airline preferences, alliances, budgets, and destination interests.
Requests and returned results may be visible to Google Flights, MCP client logs, model providers, and local process logs.
Booking URLs and vendor options can contain itinerary parameters that should not be shared publicly when travel plans are sensitive.
Avoid entering passport data, loyalty account credentials, payment details, traveler names, or private booking confirmations into prompts.
Prerequisites
Python 3.10 or newer with pipx, pip, or another Python package runner.
MCP optional dependencies installed, for example with `pipx install "flights[mcp]"`.
Network access to Google Flights endpoints from the machine running the MCP server.
Review of Google Flights terms, travel-search rate limits, and internal travel-data policies.
Agreement on whether route, date, passenger, cabin, alliance, and fare queries may be sent to Google and the MCP client.
Fli is a Google Flights MCP server, CLI, and Python library. It lets Claude and
other MCP clients search one-way and round-trip flights, flexible travel dates,
airports, and booking options using a reverse engineered Google Flights API
workflow.
Use it when an agent needs structured flight-search context before a human
checks current fare details. Fli can return flight options, prices, currencies,
legs, cabin filters, airline and alliance filters, layover constraints, airport
search results, Google Flights deep links, and vendor booking options when
available.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, PyPI package page, license, Python package metadata, MCP guide, MCP
server, MCP entrypoint wrapper, search client, and flight-search implementation
for current installation, tool, and request behavior.
Ask Claude to compare one-way or round-trip options for a route and date.
Search flexible date ranges for cheaper travel windows.
Filter by cabin class, maximum stops, departure window, airline, alliance, or
layover duration.
Resolve airport codes before searching.
Retrieve booking links and vendor options for a flight found by
search_flights.
Generate a structured shortlist that a traveler can verify in Google Flights
or with an airline.
Safety and Privacy
Fli is not an official Google Flights API. It relies on reverse engineered API
behavior, browser-like request handling, rate limiting, and retries. Review
Google Flights terms and keep automated search volume reasonable.
Flight information changes quickly. Prices, seats, schedules, baggage fees,
fare classes, booking links, and vendor availability must be verified in Google
Flights, the airline site, or the booking provider before a traveler acts.
Searches can disclose travel intent. Keep sensitive trips, traveler identities,
loyalty accounts, passport data, payment details, and private booking
confirmations out of prompts and MCP configuration.
Duplicate Check
No Fli entry, punitarani/fli, Google Flights MCP entry, flights package
entry, or matching source URL was found in content/mcp.
Show that Fli Google Flights MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/fli-google-flights-mcp-server)
How it compares
Fli Google Flights MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
1 trust signal differ across this comparison (Submitter).
Google Flights MCP server, CLI, and Python library for searching flights, flexible travel dates, airports, and booking options through a reverse engineered Google Flights API workflow.
Connect Claude to a Google Colab runtime. Colab MCP starts a local FastMCP server and websocket proxy, waits for an authorized Colab-origin browser connection, then exposes the session's notebook and runtime tools to your MCP client over stdio.
MCP server for Google Search Console that lets Claude list properties, inspect indexing status, query search analytics, compare performance periods, audit sitemaps, and manage Search Console resources with guarded destructive tools.
✓Fli is not an official Google project; upstream describes reverse engineered Google Flights API access.
Flight availability, fares, booking options, baggage fees, cabin details, and vendor links can change quickly and must be verified on the airline or booking provider before purchase.
The search client impersonates browser-like requests, rate limits calls, and retries failures; excessive automated searches may be blocked or violate service expectations.
The MCP server returns booking links but does not buy tickets, spend money, or manage reservations.
Travel results should not be treated as legal, immigration, visa, safety, or airline-policy advice.
✓User-entered trip details are sent to Ignav to retrieve live flight prices and booking links.
✓Colab MCP runs a local websocket proxy and waits for a Google Colab browser session to connect before proxying session tools.
The server creates a bearer-style proxy token and accepts a single authorized Colab-origin websocket connection at a time.
A connected Colab runtime can execute code and interact with notebooks, outputs, files, variables, packages, and mounted resources depending on the session and tools exposed by Colab.
Use disposable notebooks or reviewed development sessions before allowing Claude to run code or inspect outputs.
Avoid connecting notebooks that have access to production data, cloud credentials, private datasets, paid accelerators, or long-running jobs unless the workflow has explicit approval.
✓The server requests the Google Search Console webmasters scope and can access every property available to the authenticated account.
add_site, delete_site, and delete_sitemap are disabled by default and only run when GSC_ALLOW_DESTRUCTIVE is true.
manage_sitemaps can submit or delete sitemaps depending on action and destructive settings.
URL inspection and analytics tools can reveal indexing issues, search terms, landing pages, countries, devices, click-through rates, and ranking positions.
Use least-privilege service accounts, avoid full-access credentials where read-only analysis is enough, and confirm exact site_url values with list_properties.
Privacy notes
✓Search queries can reveal travel plans, home or work locations, dates, passenger counts, cabin preferences, airline preferences, alliances, budgets, and destination interests.
Requests and returned results may be visible to Google Flights, MCP client logs, model providers, and local process logs.
Booking URLs and vendor options can contain itinerary parameters that should not be shared publicly when travel plans are sensitive.
Avoid entering passport data, loyalty account credentials, payment details, traveler names, or private booking confirmations into prompts.
✓Trip data provided by users is shared with Ignav solely to retrieve flight search results.
✓Notebook code, prompts, outputs, logs, variables, datasets, file paths, runtime metadata, package lists, browser session details, and generated websocket tokens can be visible to the MCP client and model provider.
Colab notebooks may contain API keys, OAuth tokens, mounted Drive paths, secrets in environment variables, private model weights, customer data, or unpublished research.
Local log files are created under a temporary Colab MCP log directory by default unless a log directory is specified.
Review Google Colab, MCP client, model provider, and organization retention policies before sending notebook or runtime context to an assistant.
✓OAuth client secrets, service account JSON, cached token files, Search Console properties, page URLs, query terms, sitemap URLs, countries, devices, clicks, impressions, CTR, and positions can be sensitive.
The server stores OAuth tokens under a user config directory unless GSC_CONFIG_DIR is changed.
Service account files and OAuth tokens must stay out of prompts, issue comments, logs, screenshots, and repository files.
Redact property URLs, query data, page URLs, tokens, credential file paths, and inspection results before sharing MCP transcripts.
Prerequisites
Python 3.10 or newer with pipx, pip, or another Python package runner.
MCP optional dependencies installed, for example with `pipx install "flights[mcp]"`.
Network access to Google Flights endpoints from the machine running the MCP server.
Review of Google Flights terms, travel-search rate limits, and internal travel-data policies.
Claude Code or another MCP client that supports remote HTTP servers.
uv or uvx available to run the server from the GitHub repository.
Local MCP client that supports `notifications/tools/list_changed`.
Google Colab account and browser session you are authorized to use.
Local machine access, because upstream documents that the MCP client must run locally.
Google Cloud project with the Search Console API enabled.
OAuth desktop client secrets JSON or service account JSON stored outside the repository.
Google Search Console properties where the authenticated user or service account has access.
MCP client that can run uvx or a local Python clone.
Install
pipx install "flights[mcp]"
claude mcp add --transport http ignav https://ignav.com/mcp
uvx git+https://github.com/googlecolab/colab-mcp
Run `uvx mcp-search-console` with either `GSC_OAUTH_CLIENT_SECRETS_FILE` for OAuth or `GSC_CREDENTIALS_PATH` plus `GSC_SKIP_OAUTH=true` for a service account.