Ext Ops Panel
Open dashboard
Comparison

Mapbox Developer vs TfL MCP Server

Mapbox Developer is an MCP server published by mapbox. Marketplaces we read that list it: 1 (Docker MCP Catalog). TfL MCP Server is a plugin bundle for AI coding tools published by oneill9. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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
MarketplaceMapbox DeveloperTfL MCP Server
Docker MCP Catalog Listed
Version: sha256:4dd53e90855e
Forks (GitHub): 11
Pulls (Docker Hub): 14 257
Stars (Docker Hub): 1
Stars (GitHub): 61
Not marked · First seen
Not listed
Community marketplace oneill9/mcp-server-tfl Not listed Listed
Version: 2.0.0
No figure published
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 Developer vs TfL MCP Server
FactMapbox DeveloperTfL MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)61No figure on GitHub
Pulls (Docker Hub) (differs)14 257No figure on Docker Hub
Forks (GitHub) (differs)11No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/mapbox-devkit)On your machine (@oneill9/tfl-mcp-server)
Transport (differs)stdioNot stated
Tools it declares (differs)23Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle7
LicenceMITMIT
Repository (differs)github.com/mapbox/mcp-devkit-servergithub.com/oneill9/mcp-server-tfl
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14

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 Developer

In its own words, on Docker MCP Catalog:

Direct access to Mapbox developer APIs for AI assistants. Enables style management, token management, GeoJSON preview, and other developer tools for building Mapbox applications.

TfL MCP Server

In its own words, on Community GitHub marketplaces:

Real-time London transport data — service status, arrivals, journey planning, fares, crowding, and bike points via the TfL Unified API.

How to run each

Mapbox Developer As a local MCP server: Docker image

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

Requires: MAPBOX_ACCESS_TOKEN (secret)

TfL MCP Server As a Codex plugin

Codex
codex plugin marketplace add oneill9/mcp-server-tfl

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

Tools each declares

The marketplaces of TfL MCP Server publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Mapbox Developer · What it can do: TfL MCP Server · 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