Mapbox vs com.mireye/earth
Mapbox is an MCP server published by mapbox. Marketplaces we read that list it: 1 (Docker MCP Catalog). com.mireye/earth is an MCP server published by mireye.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  Mapbox |  com.mireye/earth |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:298701beaeed Forks (GitHub): 44 Pulls (Docker Hub): 35 394 Stars (Docker Hub): 2 Stars (GitHub): 360 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.5.0 Downloads/month (PyPI): 204 Downloads/week (PyPI): 37 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 | Mapbox | com.mireye/earth |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 360 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 35 394 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 44 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/mapbox) | Remote server (api.mireye.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 28 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 4, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/mapbox/mcp-server | github.com/mireye-labs/mireye-earth-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 29 h ago, requires a key |
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
Mapbox
Transform any AI agent into a geospatially-aware system with Mapbox APIs. Provides geocoding, POI search, routing, travel time matrices, isochrones, and static map generation.
com.mireye/earth
MCP server for Mireye Earth — federal-source-cited geospatial data for any MCP-aware agent.
How to run each
Mapbox As a local MCP server: Docker image
claude mcp add --env "MAPBOX_ACCESS_TOKEN=<YOUR_MAPBOX_ACCESS_TOKEN>" --transport stdio mapbox -- docker run -i --rm -e MAPBOX_ACCESS_TOKEN mcp/mapboxRequires: MAPBOX_ACCESS_TOKEN (secret)
com.mireye/earth As a remote MCP server
claude mcp add --transport http earth https://api.mireye.com/mcpRequires: MIREYE_BEARER_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.mireye/earth has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of com.mireye/earth publish no list of tools, so we do not compare tools.
Settings each asks for
Only Mapbox asks for
MAPBOX_ACCESS_TOKEN (secret)
Only com.mireye/earth asks for
MIREYE_BASE_URLMIREYE_BEARER_TOKEN (secret)MIREYE_MCP_CREDENTIALS_FILEMIREYE_TIMEOUT_S
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Mapbox · What it can do: com.mireye/earth · 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.