Ext Ops Panel
Open dashboard
Comparison

Mapbox vs geonovum

Mapbox is an MCP server published by mapbox. Marketplaces we read that list it: 1 (Docker MCP Catalog). geonovum is a plugin bundle for AI coding tools published by MinBZK. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
MarketplaceMapboxgeonovum
Docker MCP Catalog Listed
Version: sha256:298701beaeed
Forks (GitHub): 44
Pulls (Docker Hub): 35 414
Stars (Docker Hub): 2
Stars (GitHub): 360
Not marked · First seen
Not listed
Community marketplace djimit/overheid-plugins Not listed Listed
Version: 0.4.5
Forks (GitHub): 2
Stars (GitHub): 2
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

Mapbox vs geonovum
FactMapboxgeonovum
Marketplaces that list it11
Stars (GitHub) (differs)360 (better)2 (worse)
Pulls (Docker Hub) (differs)35 414No figure on Docker Hub
Forks (GitHub) (differs)44 (better)2 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/mapbox)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)28Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle6
Licence (differs)MITNot stated
Repository (differs)github.com/mapbox/mcp-servergithub.com/minbzk/geonovum-plugin
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-16

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

In its own words, on Docker MCP Catalog:

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.

geonovum

In its own words, on Community GitHub marketplaces:

CONCEPT — Skills voor Nederlandse geo-standaarden (beheerd door Geonovum): OGC API services (WMS, WFS, WMTS, OGC API Features), metadata (ISO 19115, NGR), informatiemodellen (NEN 3610, MIM), INSPIRE implementatie en 3D standaarden (CityGML, 3D Tiles).

How to run each

Mapbox As a local MCP server: Docker image

Claude Code
claude mcp add --env "MAPBOX_ACCESS_TOKEN=<YOUR_MAPBOX_ACCESS_TOKEN>" --transport stdio mapbox -- docker run -i --rm -e MAPBOX_ACCESS_TOKEN mcp/mapbox

Requires: MAPBOX_ACCESS_TOKEN (secret)

geonovum As a Claude Code plugin

Claude Code
/plugin marketplace add djimit/overheid-plugins
/plugin install geonovum@overheid-plugins

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

Tools each declares

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

Settings each asks for

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

What it can do: Mapbox · What it can do: geonovum · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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