blueprint-modular
Related Servers
Alternatives to blueprint-modular
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for the NS UI React component registry. Search components, inspect source and details, list categories, get install commands, and retrieve design-token conventions.13 npm34MIT
- AlicenseAqualityAmaintenanceRead-only MCP server that exposes a design system's tokens, components, conventions, and deprecations as queryable tools, enabling agents to look up canonical values, assess change impact, and detect hardcoded value drift.82 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides a real API for coding agents to look up design system components, props, and tokens, preventing guessed answers.9MIT
- FlicenseNot gradedqualityAmaintenanceGrounds coding agents' UI work in real product screens by exposing catalogue tools that return reference screens as inline images, license-cleared fonts and icons, and the recorded design system behind a web screen, alongside a bundled design-skill workflow, resources, and token-free diagnostics. It runs as a hosted HTTP service with account-key access or as a local stdio adapter that also serves the skill documents and playbook prompts.-
- AlicenseAqualityCmaintenanceEnables MCP clients to browse, customize, and compose UI components, design tokens, site content, and a UI/UX spec into standalone pages. Also supports searching components and retrieving specs, resources, and prompts for page generation.7MIT
- AlicenseNot gradedqualityDmaintenanceProvides resources, tools, and prompts for a Design System via MCP protocol, enabling component search, reading, and related component discovery.266 npmMIT
TDQS
Scored across 4 tools
The tools are mostly distinct: list_components and search_components both return component lists but differ in browsing vs. keyword search, and their descriptions clearly define when to use each. get_component and suggest_composition serve unique roles, so confusion is minimal.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: list_components, search_components, get_component, suggest_composition. The slight variance in nouns (components, component, composition) is semantically justified and does not break the pattern.
Four tools is well-scoped for a design system component catalog: browse, search, fetch details, and semantic composition suggestion. Each earns its place and the count feels neither thin nor bloated.
The set covers the full read-only lifecycle of the domain: discovering components (list/search), retrieving deep detail (get_component), and translating an intent into a component set (suggest_composition). No obvious gaps exist for a reference server.