Ext Ops Panel
Open dashboard
Comparison

Google Flights vs Seat Sherpa

Google Flights is an MCP server published by kgprs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Seat Sherpa is an MCP server published by seatsherpa.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 FlightsSeat Sherpa
Docker MCP Catalog Listed
Version: sha256:8ecfd55f5aff
Forks (GitHub): 0
Pulls (Docker Hub): 29 222
Stars (Docker Hub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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 Seat Sherpa
FactGoogle FlightsSeat Sherpa
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Pulls (Docker Hub) (differs)29 222No figure on Docker Hub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/google-flights)Remote server (seatsherpa.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)3Not published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/kgprs/google-flights-mcp-serverNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago

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.

Seat Sherpa

In its own words, on Official MCP Registry:

Find carpool rides in California and Nevada: live seats, times and all-in seat prices. Read-only.

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

Seat Sherpa As a remote MCP server

Claude Code
claude mcp add --transport http rides https://seatsherpa.app/mcp

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

Only Seat Sherpa has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Seat Sherpa publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Google Flights · What it can do: Seat Sherpa · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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