Google Maps Comprehensive vs LibraryAPI
Google Maps Comprehensive is an MCP server published by vicpeacock. Marketplaces we read that list it: 1 (Docker MCP Catalog). LibraryAPI is an MCP server published by libraryapi.dev. 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
| Marketplace |   Google Maps Comprehensive |  LibraryAPI |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:fc37a12a21f4 Forks (GitHub): 1 Pulls (Docker Hub): 38 499 Stars (Docker Hub): 0 Stars (GitHub): 6 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.3 Downloads/month (PyPI): 203 Downloads/week (PyPI): 43 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | Google Maps Comprehensive | LibraryAPI |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 6 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 38 499 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/google-maps-comprehensive) | On your machine (libraryapi-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 8 | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/vicpeacock/google-maps-comprehensive-mcp | github.com/library-api/libraryapi-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
Complete Google Maps integration with 8 tools including geocoding, places search, directions, elevation data, and more using Google's latest APIs.
LibraryAPI
US public libraries and branches near any address, with collections from the IMLS survey
How to run each
Google Maps Comprehensive As a local MCP server: Docker image
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-comprehensiveRequires: GOOGLE_MAPS_API_KEY (secret)
LibraryAPI As a local MCP server: PyPI package
claude mcp add --env "LIBRARYAPI_KEY=<YOUR_LIBRARYAPI_KEY>" --transport stdio libraryapi-mcp -- uvx libraryapi-mcpRequires: LIBRARYAPI_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 LibraryAPI publish no list of tools, so we do not compare tools.
Settings each asks for
Only Google Maps Comprehensive asks for
GOOGLE_MAPS_API_KEY (secret)
Only LibraryAPI asks for
LIBRARYAPI_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Google Maps Comprehensive · What it can do: LibraryAPI · 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.