google-flights-proto-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | The host interface to bind the HTTP server to. | 127.0.0.1 |
| PORT | No | The port to bind the HTTP server to. | 8010 |
| GOOGLE_FLIGHTS_MCP_SOCS_COOKIE | No | Consent cookie value to use when Google rotates its EU consent cookie. | |
| GOOGLE_FLIGHTS_MCP_BROWSER_EXECUTABLE | No | Path to a Chrome/Chromium executable to override automatic browser discovery. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_protobuf_search_urlA | Build a real |
| discover_and_rank_completeB | Use protobuf+HTTP to pair full itineraries, rank them, and return top 1-3. |
| search_and_verify_topB | Run protobuf → HTTP → pairing → ranking → top 1-3 → Playwright verification. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
build_protobuf_search_url is clearly distinct as a URL builder, but discover_and_rank_complete and search_and_verify_top overlap heavily since both perform the same core search and ranking flow, differing only in the verification step. The descriptions help, but an agent could easily pick the wrong one when it only needs unverified results.
All tool names use snake_case and begin with a verb, which is a solid pattern. The minor inconsistency is that build_protobuf_search_url uses a simple verb_noun structure while the other two use verb_and_verb_complement, making the set slightly uneven but still readable.
Three tools is a reasonable size for a focused flight-search server that exposes a small pipeline: build URL, run search and ranking, then optionally verify. Each tool has a real purpose, though the set is slightly thin if broader flight-search operations were intended.
The tools cover the main workflow from URL construction through ranking and verification, so most end-to-end flight search needs are addressed. Minor gaps exist such as no tool to view raw intermediate protobuf/HTTP responses, but agents can work around this by chaining the available tools.