Ext Ops Panel
Open dashboard
Comparison

Mapbox vs Goyondo

Mapbox is an MCP server published by mapbox. Marketplaces we read that list it: 1 (Docker MCP Catalog). Goyondo is an MCP server published by agteo. 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

Where each is published
MarketplaceMapboxGoyondo
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.1.0
Downloads/month (npm): 300
Downloads/week (npm): 300
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 Goyondo
FactMapboxGoyondo
Marketplaces that list it11
Stars (GitHub) (differs)360No figure on GitHub
Pulls (Docker Hub) (differs)35 394No figure on Docker Hub
Forks (GitHub) (differs)44No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/mapbox)On your machine (goyondo-mcp)
Transportstdiostdio
Tools it declares (differs)28Not published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/mapbox/mcp-serverNot stated
Changes in the last 7 days (differs)02
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

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.

Goyondo

In its own words, on Official MCP Registry:

Trip planner your AI assistant can plan and edit: persistent trips, group plans, booking records.

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)

Goyondo As a local MCP server: npm package

Claude Code
claude mcp add --env "GOYONDO_API_KEY=<YOUR_GOYONDO_API_KEY>" --transport stdio goyondo -- npx -y goyondo-mcp

Requires: GOYONDO_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 Goyondo publish no list of tools, so we do not compare tools.

Settings each asks for

Only Mapbox asks for

  • MAPBOX_ACCESS_TOKEN (secret)

Only Goyondo asks for

  • GOYONDO_API_KEY (secret)

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

What it can do: Mapbox · What it can do: Goyondo · 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