Ext Ops Panel
Open dashboard
Comparison

Amazon Location Service vs Google Maps MCP Server

Amazon Location Service is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Google Maps MCP Server is an MCP server published by cablate. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplaceAmazon Location ServiceGoogle Maps MCP Server
Docker MCP Catalog Listed
Version: sha256:a84810ffd306
Forks (GitHub): 1 805
Pulls (Docker Hub): 13 400
Stars (Docker Hub): 0
Stars (GitHub): 9 773
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.0.69
Downloads/month (npm): 8 855
Downloads/week (npm): 964
Forks (GitHub): 94
Stars (GitHub): 471
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

Amazon Location Service vs Google Maps MCP Server
FactAmazon Location ServiceGoogle Maps MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)9 773 (better)471 (worse)
Pulls (Docker Hub) (differs)13 400No figure on Docker Hub
Forks (GitHub) (differs)1 805 (better)94 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/aws-location-mcp-server)On your machine (@cablate/mcp-google-map)
Transportstdiostdio
Tools it declares (differs)8Not published
Environment variables it asks for (differs)5, secrets among them: 22, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/mcpgithub.com/cablate/mcp-google-map
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

Amazon Location Service

In its own words, on Docker MCP Catalog:

Place search, geocoding, and route optimization.

Google Maps MCP Server

In its own words, on Official MCP Registry:

18 Google Maps tools for AI agents — geocode, search, directions, weather, and more.

How to run each

Amazon Location Service As a local MCP server: Docker image

Claude Code
claude mcp add --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --env "AWS_SESSION_TOKEN=<YOUR_AWS_SESSION_TOKEN>" --transport stdio aws-location -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN mcp/aws-location-mcp-server

Requires: AWS_SECRET_ACCESS_KEY (secret), AWS_SESSION_TOKEN (secret)

Google Maps MCP Server As a local MCP server: npm package

Claude Code
claude mcp add --env "GOOGLE_MAPS_API_KEY=<YOUR_GOOGLE_MAPS_API_KEY>" --transport stdio google-map -- npx -y @cablate/mcp-google-map

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

The marketplaces of Google Maps MCP Server publish no list of tools, so we do not compare tools.

Settings each asks for

Only Amazon Location Service asks for

  • AWS_ACCESS_KEY_ID
  • AWS_PROFILE
  • AWS_REGION
  • AWS_SECRET_ACCESS_KEY (secret)
  • AWS_SESSION_TOKEN (secret)

Only Google Maps MCP Server asks for

  • GOOGLE_MAPS_API_KEY (secret)
  • GOOGLE_MAPS_ENABLED_TOOLS

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Amazon Location Service · What it can do: Google Maps MCP Server · 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