HasData Google Flights

Google Flights MCP Server

A hosted Google Flights MCP server that gives Claude, Cursor, Windsurf and any other MCP client one Google Flights tool. Search one-way, round-trip and multi-city itineraries with fares, flight legs, carbon emissions and price history, all as structured JSON, with no Google account and no retired travel API to work around.

1,000 free credits every month, no card required, which is about 66 flight searches.

https://mcp.hasdata.com/mcp?apis=google_travel_flights

• Prompts and resources

Contents

• What you need
• Quick start
• Example prompts
• Tools
• Errors and failure paths
• Pricing, free tier and limits
• Tool selection
• How it compares
• FAQ
• HasData links
• Development
• Contributing
• License

What you need

An MCP client and a HasData API key from the dashboard, free to create with no card, and the free tier covers about 66 calls a month at the 15-credit rate. This is a remote server, so the simplest path is a URL and an x-api-key header, with no container to run and no Google account anywhere in the flow. A client that only speaks stdio reaches it through a thin launcher, published as @hasdata/google-flights-mcp on npm and hasdata-google-flights-mcp on PyPI, shown below.

Quick start

The server URL is the same for every client. We run it hands-on in Claude Code and Claude Desktop. The other blocks follow each client's own documented format for a remote server.

Clients with OAuth support can add the same URL as a connector and sign in without putting a key in a config file.

Claude Code

claude mcp add --transport http google-flights "https://mcp.hasdata.com/mcp?apis=google_travel_flights" \

--header "x-api-key: HASDATA_API_KEY"

Claude Desktop

Settings, then Connectors, then Add custom connector, then paste https://mcp.hasdata.com/mcp?apis=google_travel_flights and sign in.

For the config-file route, Claude Desktop loads only local (stdio) servers, so it reaches a remote server through a stdio launcher. The @hasdata/google-flights-mcp package is that launcher, and it reads the key from the environment. Add this to claude_desktop_config.json:

{

"mcpServers": { "google-flights": { "command": "npx", "args": ["-y", "@hasdata/google-flights-mcp"], "env": { "HASDATA_API_KEY": "YOUR_KEY" } } } }

For Python instead of Node, swap the launcher for the PyPI package, which uvx runs without a manual install:

{

"mcpServers": { "google-flights": { "command": "uvx", "args": ["hasdata-google-flights-mcp"], "env": { "HASDATA_API_KEY": "YOUR_KEY" } } } }

Cursor

~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:

{

"mcpServers": { "google-flights": { "url": "https://mcp.hasdata.com/mcp?apis=google_travel_flights", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }

Windsurf

~/.codeium/windsurf/mcp_config.json. Windsurf calls the field serverUrl, not url:

{

"mcpServers": { "google-flights": { "serverUrl": "https://mcp.hasdata.com/mcp?apis=google_travel_flights", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }

VS Code

.vscode/mcp.json in the workspace:

{

"servers": { "google-flights": { "type": "http", "url": "https://mcp.hasdata.com/mcp?apis=google_travel_flights", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }

Example prompts

Prompts, not code. Paste one in and the agent picks the tool itself. Each is annotated with the calls it takes, because every successful call costs 15 credits.

Find one-way flights from JFK to London Heathrow on September 15, sorted by price, and give me the three cheapest with airline and carbon estimate.

*One call, 15 credits. Fares, legs and emissions all come back together.*

Same route but non-stop only, in business class, and tell me which option has the lowest emissions.

*One call, 15 credits. Cabin and stops are filters on the one request.*

Is $295 a good price for JFK to LHR right now, given the price history?

*One call, 15 credits. The response carries priceInsights with a typical range and a price level.*

Round trip JFK to LHR, out September 15 back September 22, cheapest fare.

*Two calls, 30 credits. Google returns outbound options first, then the return leg is a second call keyed by the option you pick.*

A round trip is two calls by design. The first returns outbound itineraries each with a departureToken, and you pass that token back to get the matching return flights. One-way and the price check are a single call each.

Tools

One tool, read-only. The sample below is trimmed from a real call, and fares move constantly. Read it as a shape. The tool name links to its endpoint reference, which carries the full parameter list.

The sample is the payload, not the whole response. A tools/call result carries one text block, and that text is itself JSON holding url, status, text and json, with the scraped data under json. From a raw JSON-RPC response the path is result.content[0].text, parsed, then .json. A chat client unwraps that for you and code talking to the endpoint directly does not.

Get Google Flights results

hasdata_google_travel_flights_getGoogleFlights

Itineraries for a route and date, with fares, legs, emissions and price history.

The reference also documents includeConnections, excludeConnections, layoverDuration, outboundTimes, returnTimes, showHidden, lessEmissions and multiCityJson.

Results split into bestFlights and otherFlights. Each itinerary carries price, type, totalDuration in minutes, a flights array of legs, a carbonEmissions object, and a bookingToken. Each leg holds the departureAirport and arrivalAirport (each with id, name and local time), duration, airline, flightNumber, airplane, legroom, travelClass, an extensions array, and oftenDelayedByOver30Min on legs Google flags. A non-stop itinerary has one leg, a connection has several.

carbonEmissions is in grams, not kilograms. thisFlight: 433000 is 433 kg. differencePercent compares it to typicalForThisRoute, so a negative number is a greener-than-average flight.

{

"price": 295, "type": "One way", "totalDuration": 415, "flights": [ { "departureAirport": { "id": "JFK", "name": "John F. Kennedy International Airport", "time": "2026-09-15 8:15" }, "arrivalAirport": { "id": "LHR", "name": "Heathrow Airport", "time": "2026-09-15 20:10" }, "duration": 415, "airline": "Virgin Atlantic", "flightNumber": "VS 26", "airplane": "Boeing 787", "travelClass": "Economy" } ], "carbonEmissions": { "thisFlight": 367000, "typicalForThisRoute": 419000, "differencePercent": -12 }, "bookingToken": "W1t7..." }

priceInsights sits alongside the itineraries with lowestPrice, a typicalPriceRange, a priceLevel such as typical, and a priceHistory of [timestamp, price] points. airports echoes the resolved departure and arrival airports with city and country.

Prompts and resources

The server ships one prompt, a ready-made workflow a client can offer instead of making the user compose a tool call.

Alongside them the server exposes 7 resources, one per parameter whose accepted values are a fixed list. Reading one is cheaper than learning the vocabulary from a rejected call, and it costs no credits. Each URI is hasdata://google_travel_flights/ .

| currency