Ext Ops Panel
Open dashboard
Comparison

Google Flights vs Google Maps Comprehensive

Google Flights is an MCP server published by kgprs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Google Maps Comprehensive is an MCP server published by vicpeacock. Marketplaces we read that list it: 1 (Docker MCP Catalog). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceGoogle FlightsGoogle Maps Comprehensive
Docker MCP Catalog Listed
Version: sha256:8ecfd55f5aff
Forks (GitHub): 0
Pulls (Docker Hub): 28 127
Stars (Docker Hub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: sha256:fc37a12a21f4
Forks (GitHub): 1
Pulls (Docker Hub): 38 499
Stars (Docker Hub): 0
Stars (GitHub): 6
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Google Flights vs Google Maps Comprehensive
FactGoogle FlightsGoogle Maps Comprehensive
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)6 (better)
Pulls (Docker Hub) (differs)28 127 (worse)38 499 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/google-flights)On your machine (mcp/google-maps-comprehensive)
Transportstdiostdio
Tools it declares (differs)38
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/kgprs/google-flights-mcp-servergithub.com/vicpeacock/google-maps-comprehensive-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Google Flights

In its own words, on Docker MCP Catalog:

Interact with Google Flights data to search for one-way, round-trip, and date range flight options between airports.

Google Maps Comprehensive

In its own words, on Docker MCP Catalog:

Complete Google Maps integration with 8 tools including geocoding, places search, directions, elevation data, and more using Google's latest APIs.

How to run each

Google Flights As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio google-flights -- docker run -i --rm mcp/google-flights

Google Maps Comprehensive As a local MCP server: Docker image

Claude Code
claude mcp add --env "GOOGLE_MAPS_API_KEY=<YOUR_GOOGLE_MAPS_API_KEY>" --transport stdio google-maps-comprehensive -- docker run -i --rm -e GOOGLE_MAPS_API_KEY mcp/google-maps-comprehensive

Requires: GOOGLE_MAPS_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Only Google Flights declares

  • find_all_flights_in_range
  • get_flights_on_date
  • get_round_trip_flights

Only Google Maps Comprehensive declares

  • maps_directions
  • maps_distance_matrix
  • maps_elevation
  • maps_geocode
  • maps_ping
  • maps_place_details
  • maps_reverse_geocode
  • maps_search_places

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of Google Flights publish no settings it asks for, so we do not compare settings.

What it can do: Google Flights · What it can do: Google Maps Comprehensive · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built