Ext Ops Panel
Open dashboard
Comparison

bridge-ds vs Brandsystem MCP — Brand Guidelines for AI

bridge-ds is a plugin bundle for AI coding tools published by noemuch. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Brandsystem MCP — Brand Guidelines for AI is an MCP server published by Brandcode-Studio. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplacebridge-dsBrandsystem MCP — Brand Guidelines for AI
Claude Code: claude-plugins-community Listed
Version: 6.0.0
Forks (GitHub): 15
Stars (GitHub): 156
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.16.1
Downloads/month (npm): 860
Downloads/week (npm): 95
Forks (GitHub): 1
Stars (GitHub): 15
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

bridge-ds vs Brandsystem MCP — Brand Guidelines for AI
Factbridge-dsBrandsystem MCP — Brand Guidelines for AI
Marketplaces that list it11
Stars (GitHub) (differs)156 (better)15 (worse)
Forks (GitHub) (differs)15 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (figma-console-mcp)On your machine (@brandsystem/mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)7Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/noemuch/bridgegithub.com/brandcode-studio/brandsystem-mcp
Changes in the last 7 days00
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

bridge-ds

In its own words, on Claude Code: claude-plugins-community:

AI-powered design generation in Figma using your real design system. Bridge extracts your DS (components, tokens, styles), writes validated specs, and generates production-ready Figma designs with 100% DS compliance — zero hardcoded values, real component instances, bound variables. Features a unique learning loop that captures your corrections and improves future generations. Supports both figma-console-mcp and the official Figma MCP server.

Brandsystem MCP — Brand Guidelines for AI

In its own words, on Official MCP Registry:

Use existing brand guidelines with AI. Turn websites, PDFs, and Figma into a .brand runtime.

How to run each

bridge-ds As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install bridge-ds@claude-community

Brandsystem MCP — Brand Guidelines for AI As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio brandsystem-mcp -- npx -y @brandsystem/mcp

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Brandsystem MCP — Brand Guidelines for AI publish no settings it asks for, so we do not compare settings.

What it can do: bridge-ds · What it can do: Brandsystem MCP — Brand Guidelines for AI · 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.

Where the data comes from: how the catalog is built