HasData Google Flights

What HasData Google Flights MCP server does

The HasData Google Flights MCP server lets an MCP-compatible client search Google Flights for available itineraries. Results include each itinerary's price and currency, total duration, stop count, flight legs, airline and flight number, aircraft, departure and arrival airports and times, carbon emissions, and price-history information. The response is structured JSON rather than a conversational summary.

Searches can be one-way, round-trip, or multi-city. Filters cover cabin class, number of stops, sorting, passenger counts, maximum price, maximum duration, bags, airlines to include or exclude, currency, country, language, and deeper search behavior. Route endpoints accept IATA airport codes, and location knowledge graph identifiers can also be used.

How it works

The HasData Google Flights MCP server is hosted at https://mcp.hasdata.com/mcp?apis=google_travel_flights and uses streamable HTTP. Clients authenticate with an x-api-key header containing a HasData API key. No container or Google account is required for the remote setup.

It exposes one read-only tool: hasdata_google_travel_flights_getGoogleFlights. A one-way search normally uses one call. Round trips use two calls: the first obtains outbound options and a departureToken, and a later call uses the selected token to retrieve matching return flights. Booking options can be requested with a bookingToken. Each successful call costs 15 credits.

Direct MCP responses contain a text block whose contents are JSON. For code calling the endpoint directly, the scraped data is nested under the parsed json property; chat clients generally unwrap this response.

Setup and configuration

Create a HasData API key through the HasData dashboard. The free tier provides 1,000 credits each month, described in the README as approximately 66 calls at the 15-credit rate. Configure the remote endpoint and send the key as an HTTP header.

Claude Code, Cursor, Windsurf, and VS Code can be configured with the remote URL directly. Claude Desktop can use its connector flow for the remote endpoint. Its local configuration-file route requires a launcher: either the npm package @hasdata/google-flights-mcp through npx, or the PyPI package hasdata-google-flights-mcp through uvx; both read HASDATA_API_KEY from the environment.

Clients with OAuth support may add the same endpoint as a connector and sign in without placing an API key in a configuration file, as described by the project.

Tools and capabilities

The HasData Google Flights MCP server provides:

• Route and date searches using airport codes or location identifiers.
• One-way, round-trip, and multi-city itinerary queries.
• Sorting by price, duration, emissions, departure time, arrival time, or top flights.
• Filters for stops, travel class, passengers, price, duration, baggage, and airlines.
• Fare, itinerary-leg, aircraft, timing, emissions, and price-history data.
• Return-flight and booking-option retrieval using tokens from earlier results.

Limitations and notes

The server has one tool and is read-only. Round-trip searches consume two calls by design, while one-way searches and price checks use one call in the documented examples. Every successful call costs 15 credits, so applications should account for the monthly allowance and token-based follow-up calls.

Fares change frequently, and the README presents returned data as a current result shape rather than a guaranteed price. The tool returns search data; the provided material does not describe booking completion or ticket purchase operations. Airline inclusion and exclusion are mutually exclusive parameters for a request.