Mapbox Developer vs architecture-studio
Mapbox Developer is an MCP server published by mapbox. Marketplaces we read that list it: 1 (Docker MCP Catalog). architecture-studio is a plugin bundle for AI coding tools published by AlpacaLabsLLC. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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
| Marketplace |  Mapbox Developer |  architecture-studio |
|---|---|---|
| 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 |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.4.1 Forks (GitHub): 80 Stars (GitHub): 377 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
| Fact | Mapbox Developer | architecture-studio |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 61 (worse) | 377 (better) |
| Pulls (Docker Hub) (differs) | 14 257 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 (worse) | 80 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/mapbox-devkit) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 23 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Hooks it runs (differs) | Not published | 4 |
| Parts of the bundle (differs) | Not a bundle | 63 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/mapbox/mcp-devkit-server | github.com/alpacalabsllc/skills-for-architects |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
Direct access to Mapbox developer APIs for AI assistants. Enables style management, token management, GeoJSON preview, and other developer tools for building Mapbox applications.
architecture-studio
Description: Architecture Studio is a Claude plugin system for architects, designers, and AEC professionals. It includes 7 autonomous agents, 36 skills, 6 rules, and 3 hooks organized into 9 installable plugins — covering site research, NYC property due diligence, zoning envelope analysis, workplace programming, CSI specifications, sustainability (EPD parsing and comparison), FF&E product research, and presentation generation. A single entry point (`/studio`) routes users to the right agent or skill based on natural language. Agents orchestrate multiple skills, exercise judgment, and hand off to each other across the project lifecycle. Skills ship with bundled reference data — NYC Zoning Resolution chapters, IBC occupancy load factors, workplace benchmarks, and Uruguay zoning regulations. Key features: - `/studio` smart router — describe your task, get routed automatically - 7 agents with handoff logic (site planner → zoning expert → workplace strategist → materials researcher → FF&E designer → sustainability
How to run each
Mapbox Developer As a local MCP server: Docker image
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-devkitRequires: MAPBOX_ACCESS_TOKEN (secret)
architecture-studio As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install architecture-studio@claude-communityCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of architecture-studio publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of architecture-studio publish no settings it asks for, so we do not compare settings.
What it can do: Mapbox Developer · What it can do: architecture-studio · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.