Google Flights
Let your coding agent query Google Flights for routes, fare grids, and airport codes while you prototype travel tools or plan founder trips.
Overview
com.pulsemcp/google-flights is an MCP server for the Build phase that exposes Google Flights search, flexible-date pricing grids, and airport lookup to your agent over stdio.
What is this MCP server?
- stdio MCP server installable via npx google-flights-mcp-server (v0.2.4)
- Flight search across origin, destination, and dates
- Date-grid style pricing exploration for flexible travel dates
- Airport lookup and code resolution for itinerary planning
- Experimental PulseMCP package under pulsemcp/mcp-servers
- Server schema version 0.2.4
- stdio transport via npm package google-flights-mcp-server
- Repository subfolder experimental/google-flights on pulsemcp/mcp-servers
Community signal: 70 GitHub stars.
What problem does it solve?
You want flight and airport data inside the agent loop without maintaining a custom scraper or bouncing between browser tabs.
Who is it for?
Indie builders prototyping travel widgets, internal trip planners, or agent demos that need live flight search context.
Skip if: Production OTAs, regulated booking flows, or teams that need contracted airline APIs and SLAs.
What do I get? / Deliverables
Your agent can answer itinerary and fare questions from MCP tools while you build or spec travel-related features.
- Registered MCP server entry pointing at google-flights-mcp-server
- Agent-callable tools for flight search and airport resolution
- Documented origin-destination-date queries in your project prompts
Recommended MCP Servers
Journey fit
Flight search is an external data integration you wire in during product build, not a shipping or ops workflow by default. Canonical shelf is integrations because the server exposes search and lookup tools to the agent runtime via MCP stdio.
How it compares
MCP flight-search integration, not a commercial flights API or a Claude skill markdown workflow.
Common Questions / FAQ
Who is com.pulsemcp/google-flights for?
Solo and indie developers using MCP agents who need Google Flights search and airport lookup during build and integration work.
When should I use com.pulsemcp/google-flights?
Use it while wiring travel data into an agent, comparing routes for a prototype, or automating founder travel research from the IDE.
How do I add com.pulsemcp/google-flights to my agent?
Register the stdio server with npx -y google-flights-mcp-server in your Claude Code or Cursor MCP config using the published npm package identifier.