Refero MCPofficial
A
licenseA
qualityB
maintenanceEnables searching the Refero design catalog in plain English and generates DESIGN.md files for any project.
6
60 npm
19
MIT
refero-design-mcp
by DarCas
Related Servers
Alternatives to refero-design-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceSearches design platforms for UI references and extracts design tokens such as colors, typography, spacing, and shadows from live websites.5MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to search public design-system catalogs and retrieve only the relevant tokens or sections for a chosen brand, so generated UI matches a specified visual style instead of generic AI output.827 npm1BSD 3-Clause
- FlicenseNot gradedqualityBmaintenanceEnables intent-based semantic search over external design system documentation, allowing MCP-compatible AI assistants to retrieve relevant design tokens, component architectures, and code patterns via a single tool.-
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to query any DESIGN.md design system and receive short, targeted answers with exact design tokens, existing component classes, markup examples, and rules. It also catches drift by flagging made-up colors and pixel values and suggesting the nearest token.1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search, understand, and generate code for design system components by syncing and indexing a component library.ISC
TDQS
A4.1/5.0
Scored across 6 tools
Disambiguation4/5
Search vs match overlap somewhat (both find styles), but descriptions clearly separate keyword matching from qualitative brief matching. The two retrieval tools (get_design_md for prose, get_style for JSON tokens) are explicitly differentiated, and index_status/list_style_ids target distinct metadata concerns.
Naming Consistency5/5
Every tool follows the identical refero_<verb>_<noun> pattern: refero_search_styles, refero_match_style, refero_get_style, refero_list_style_ids, etc. No camelCase or naming deviations; totally predictable.
Tool Count5/5
Six tools is well-scoped for a design-style discovery and retrieval server, with each tool earning its place across discovery, matching, and rendering. No redundancy or bloat.
Completeness4/5
Covers the full read lifecycle: discover ids, search, brief-match, fetch JSON tokens, and render prose. Being a read-only scraper of a public site, no CRUD is needed, though minor gaps (e.g. pagination/batch retrieval) exist.
Maintenance
ActivityNo data
ResponsivenessSyncing