Ext Ops Panel
Open dashboard
Comparison

Google Maps Comprehensive vs apify

Google Maps Comprehensive is an MCP server published by vicpeacock. Marketplaces we read that list it: 1 (Docker MCP Catalog). apify is a plugin bundle for AI coding tools published by apify. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). As of our marketplace pass on 2026-10-12. 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 Maps Comprehensiveapify
Docker MCP Catalog Listed
Version: sha256:fc37a12a21f4
Forks (GitHub): 1
Pulls (Docker Hub): 38 490
Stars (Docker Hub): 0
Stars (GitHub): 6
Not marked · First seen
Not listed
Copilot CLI: github/awesome-copilot Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
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 Maps Comprehensive vs apify
FactGoogle Maps Comprehensiveapify
Marketplaces that list it11
Stars (GitHub) (differs)6 (better)1 (worse)
Pulls (Docker Hub) (differs)38 490No figure on Docker Hub
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/google-maps-comprehensive)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)8Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/vicpeacock/google-maps-comprehensive-mcpgithub.com/apify/apify-github-copilot-plugin
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 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.

apify

In its own words, on Copilot CLI: github/awesome-copilot:

Helps devs extract data from any website with thousands of trusted scrapers, crawlers, and automations from Apify Store. Integrate ready-made Actors to access all popular social media, video, e-commerce, search engines, maps, and travel sites. Build, debug, publish, and monetize new Actors on Apify.

How to run each

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)

apify

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Tools each declares

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

Settings each asks for

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

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

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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