Ext Ops Panel
Open dashboard
Comparison

Mapbox Developer vs designfit

Mapbox Developer is an MCP server published by mapbox. Marketplaces we read that list it: 1 (Docker MCP Catalog). designfit is an MCP server published by as9978. Marketplaces we read that list it: 2 (Official MCP Registry, 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 Developerdesignfit
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
Official MCP Registry Not listed Listed
Version: 0.2.1
Downloads/month (npm): 457
Downloads/week (npm): 66
Forks (GitHub): 0
Stars (GitHub): 6
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 designfit
FactMapbox Developerdesignfit
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)61 (better)6 (worse)
Pulls (Docker Hub) (differs)14 257No figure on Docker Hub
Forks (GitHub) (differs)11 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/mapbox-devkit)On your machine (designfit)
Transportstdiostdio
Tools it declares (differs)23Not published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Parts of the bundle (differs)Not a bundle2
LicenceMITMIT
Repository (differs)github.com/mapbox/mcp-devkit-servergithub.com/as9978/designfit
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 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.

designfit

In its own words, on Official MCP Registry:

Validate AI-built front-ends against Figma by tokens and geometry, not pixels.

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)

designfit As a local MCP server: npm package

Claude Code
claude mcp add --env "FIGMA_TOKEN=<YOUR_FIGMA_TOKEN>" --transport stdio designfit -- npx -y designfit

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

Settings each asks for

Only Mapbox Developer asks for

  • MAPBOX_ACCESS_TOKEN (secret)

Only designfit asks for

  • FIGMA_TOKEN (secret)

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

What it can do: Mapbox Developer · What it can do: designfit · 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. 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