Conversation
This server provides tools to interact with Google Flights data using the bundled fast_flights library. It enables searching for one-way, round-trip, and date range flight options between airports. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
|
Reviewed the security findings, nothing to be concerned about |
| description: Interact with Google Flights data to search for one-way, round-trip, and date range flight options between airports | ||
| icon: https://www.google.com/s2/favicons?domain=google.com/travel/flights&sz=64 | ||
| source: | ||
| project: https://github.com/kgprs/Google-Flights-MCP-Server |
There was a problem hiding this comment.
question: Should we fork this into docker instead?
There was a problem hiding this comment.
I feel like if we set this precedent we'll have a bunch of public repos with MCP servers that docker didn't create under the docker org. I'm hoping that most of these are just temporary until the main server repo merges the PR that adds the Dockerfle, here's the one for this server: opspawn/Google-Flights-MCP-Server#5
| image: mcp/google-flights | ||
| type: server | ||
| meta: | ||
| category: travel |
There was a problem hiding this comment.
jfyi: I noticed we don't have this category in the web UI yet. Maybe we should add it?
There was a problem hiding this comment.
I do see categories listed on the hub page, but I'm not sure how they're mapped to the "meta: category:" field here. If they aren't mapped and those hub categories are configured somewhere else, it might get confusing to show two separate categories for each server
2 participants
MCP Server Information
Server Name: Google Flights
Repository URL: https://github.com/opspawn/Google-Flights-MCP-Server
Brief Description: Provides tools to interact with Google Flights data using the bundled fast_flights library. It enables searching for one-way, round-trip, and date range flight options between airports.
Basic Requirements
Submitter Checklist
task validate -- --name google-flightstask build -- --tools google-flightsNote: The Dockerfile for this server is currently in a PR to the upstream repository (opspawn/Google-Flights-MCP-Server#5). Once that PR is merged, the server entry should be updated to point to the main branch of the upstream repository instead of the fork.