architecture-studio vs LocalPro — Verified US Local Service Provider Data
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). LocalPro — Verified US Local Service Provider Data is an MCP server published by LocalProDev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  architecture-studio |  LocalPro — Verified US Local Service Provider Data |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.4.1 Forks (GitHub): 81 Stars (GitHub): 381 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.1.0 Forks (GitHub): 0 Stars (GitHub): 1 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 | architecture-studio | LocalPro — Verified US Local Service Provider Data |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 381 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 81 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.localpro.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 4 | Not published |
| Parts of the bundle (differs) | 63 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/alpacalabsllc/skills-for-architects | github.com/localprodev/mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days 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
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
LocalPro — Verified US Local Service Provider Data
Verified US local service providers across 10 home-services trades. Owned data, no API key.
How to run each
architecture-studio As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install architecture-studio@claude-communityLocalPro — Verified US Local Service Provider Data As a remote MCP server
claude mcp add --transport http local-services https://mcp.localpro.dev/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 LocalPro — Verified US Local Service Provider Data has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: architecture-studio · What it can do: LocalPro — Verified US Local Service Provider Data · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.