Sign in Book a demo
Back to Tools
Search API Key BYOCPro
Build Your Agent View Documentation
google-flights logo

Google Flights MCP Tools for AI Agents

Let an agent look up airports, search one-way, round-trip, and multi-city flights, and retrieve airlines and booking sites for an itinerary.

Available Tools

5 tools available in this integration

GoogleFlights.GetFlightBookingOptions

Resolve a ``booking_token`` to the airlines and OTAs selling that itinerary.

GoogleFlights.LookupAirports

Find IATA airport codes for a city, country, or airport name.

GoogleFlights.SearchFlights

Search Google Flights for one-way or round-trip itineraries.

GoogleFlights.SearchMultiCityFlights

Search Google Flights for a multi-city (open-jaw) itinerary.

GoogleFlights.SearchOneWayFlights

Retrieve flight search results for a one-way flight using Google Flights

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "find the cheapest nonstop round trip from New York to Tokyo for these dates." Arcade helps it use the right Google Flights tools without guessing airport codes, itinerary shape, or booking references.

Up to 100x fewer tokens

Google Flights search results return structured itinerary details and booking references without requiring the agent to load unrelated search pages. It gets the routes, times, prices, stops, and sellers needed to compare options.

Complete the workflow end to end

Look up the airports, search a route, compare one-way or round-trip options, inspect a multi-city itinerary, and find its sellers through one toolkit designed around the complete flight-search task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing Google Flights

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For Google Flights, you can implement some of these policies:

Access when tools are listed for a user
  • Decide which tools an agent is allowed to see at all. A tool that is never listed cannot be called, whoever is asking.
Pre-execution before each tool call
  • Inspect the inputs a call is about to run with, and block it or send it for human approval when they fall outside what the agent should do unsupervised.
Post-execution after the tool returns
  • Redact direct booking URLs and tracking parameters from GoogleFlights.GetFlightBookingOptions results, so an agent cannot send travelers to an unapproved airline or OTA.
  • Strip booking tokens and deep links from GoogleFlights.SearchFlights results before they reach the model, so flight research cannot turn into an unreviewed purchase path.
  • Redact booking tokens and provider links from GoogleFlights.SearchMultiCityFlights results, so an agent can compare open-jaw itineraries without forwarding travelers to external sellers.

How to use Google Flights with your agent

Connect Google Flights to your MCP client and follow the walkthrough from setup to your first flight search. Use the example prompts to test airport lookup, itinerary search, and booking options.

Your questions, answered

A Google Flights MCP server exposes flight search capabilities as structured tools that an AI agent can call through the Model Context Protocol. An agent can look up airports, search one-way, round-trip, and multi-city itineraries, and retrieve sellers for a selected itinerary.

Google Flights is a flight-search service rather than a first-party MCP server. Arcade provides the MCP access layer, authenticated runtime, and controls for calling Google Flights searches from supported clients.

Arcade agents can find airport codes, search one-way and round-trip flights, search multi-city itineraries, and resolve a booking reference to the airlines and online travel agencies selling that itinerary. These actions are read-only; booking a flight is not included.

The integration uses one shared API key or secret configured for the Arcade connection. It does not use per-user Google Flights OAuth permissions.

No. Users do not connect individual Google Flights accounts; the configured shared credential is used for calls, brokered by Arcade rather than exposed to the model.

Yes. Contextual Access policies can require human approval before a consequential call, redact fields from responses, or hide the integration from an agent. The Google Flights actions themselves are read-only, so they do not book or purchase flights.

Arcade proxies Google Flights API calls and does not persist your content as part of normal tool execution. The shared credential is brokered and stored encrypted at rest, and the model never receives it.

Any framework or client that can reach Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade refreshes access while the configured authorization remains valid. If the shared key or secret is revoked, rotated, or can no longer be used, calls stop until the credential is reconnected or updated.

Calls remain subject to the rate limits and quotas imposed by Google Flights and the configured Arcade integration. No separate Google Flights quota or per-call limit is specified here.

Ready to actually ship your agent?

Connect your agent to Google Flights with a shared API key, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the Google Flights Quickstart