Ext Ops Panel
Open dashboard
Comparison

Mapbox vs TableJourney food travel

Mapbox is an MCP server published by mapbox. Marketplaces we read that list it: 1 (Docker MCP Catalog). TableJourney food travel is an MCP server published by tablejourney.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
MarketplaceMapboxTableJourney food travel
Docker MCP Catalog Listed
Version: sha256:298701beaeed
Forks (GitHub): 45
Pulls (Docker Hub): 35 990
Stars (Docker Hub): 2
Stars (GitHub): 363
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.1
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

Mapbox vs TableJourney food travel
FactMapboxTableJourney food travel
Marketplaces that list it11
Stars (GitHub) (differs)363 (better)0 (worse)
Pulls (Docker Hub) (differs)35 990No figure on Docker Hub
Forks (GitHub) (differs)45 (better)0 (worse)
Last release (differs)Not published2026-10-21
Where it runs (differs)On your machine (mcp/mapbox)Remote server (tablejourney.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)28Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/mapbox/mcp-servergithub.com/lewismvaughan/tablejourney-mcp
Changes in the last 7 days (differs)05
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 h ago

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.

TableJourney food travel

In its own words, on Official MCP Registry:

Food travel in 224 cities: verified places, festivals, tours. Agents earn 50% via partner tools.

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)

TableJourney food travel As a remote MCP server

Claude Code
claude mcp add --transport http food-travel https://tablejourney.com/mcp --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: X-API-Key header

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

Only TableJourney food travel has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of TableJourney food travel publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Mapbox · What it can do: TableJourney food travel · 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