blueprint-modular
Related Servers
Alternatives to blueprint-modular
No user-submitted related servers found.
Related Servers
- 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.81 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides a real API for coding agents to look up design system components, props, and tokens, preventing guessed answers.7MIT
- AlicenseNot gradedqualityDmaintenanceProvides resources, tools, and prompts for a Design System via MCP protocol, enabling component search, reading, and related component discovery.398 npmMIT

TAAFT MCP Serverofficial
FlicenseNot gradedqualityBmaintenanceEnables searching and retrieving public catalog details across 28 tools covering AI tools, MCP servers, models, tasks, companies, events, papers, and repositories. Clients can look up entries by query or fetch full details by slug or id through a stateless, no-auth Streamable HTTP endpoint.-- AlicenseNot gradedqualityBmaintenanceProvides coding agents read-only access to the Neat Labs component and style library, enabling them to search and retrieve components, styles, themes, token roles, and preview links.MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying and retrieving public design styles from the Driftless registry, including listing, searching styles, and fetching design markdown and tokens.MIT
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.