systembridge-mcp
Related Servers
Alternatives to systembridge-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for design tokens that gives AI agents read access to design systems, enabling token resolution, listing, and component usage lookups via natural language.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes your design system components and tokens to AI agents, preventing duplicate component creation and hardcoded token values.5 npm9MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that gives AI assistants structured access to a design system's tokens, components, guidelines, and patterns, enabling them to read, lint, and author design system data.1MIT
- AlicenseNot gradedqualityAmaintenanceA read-only MCP server that provides AI coding agents with a queryable contract for design system tokens, components, patterns, and anti-patterns.6 npm1Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that connects AI clients to Figma components, design tokens, and variables from the BrixUI Design System, enabling component browsing, searching, and token retrieval.44 npmMIT
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes a design system and UX rulebook as tools, enabling AI to generate UI consistent with your design tokens, components, layout rules, accessibility guidelines, and templates. It also provides a review tool to score UI proposals against the design system.-
TDQS
Scored across 37 tools
Each tool has a clearly distinct purpose: listing dimensions/brands/themes, searching/validating/transforming tokens, auditing various aspects, generating palettes/scales/systems, diffing, and figma integration. Even overlapping areas like audits are differentiated by scope (semantic vs design vs figma usage). No two tools appear to do the same thing.
Tools follow a consistent verb_noun pattern: list_, search_, validate_, transform_, generate_, audit_, analyze_, etc. All use lowercase snake_case. The naming is predictable and easily understood.
37 tools is on the higher side, but the server covers a broad domain: token management, audit, generation, Figma sync, accessibility, documentation, etc. Each tool serves a specific need, and the count is justified by the comprehensiveness. Could be slightly trimmed, but overall reasonable.
The tool set covers nearly the entire design token lifecycle: creation (generate), reading (list, search, resolve), transformation, validaton, auditing, migration, and scaling. Missing an explicit delete/remove tool, but migration execution can handle removal. Minor gap, but overall very complete.