Refero MCPofficial
A
licenseA
qualityB
maintenanceEnables searching the Refero design catalog in plain English and generates DESIGN.md files for any project.
6
63 npm
17
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.816 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.-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to search, understand, and generate code for design system components by syncing and indexing a component library.-
- AlicenseNot gradedqualityCmaintenanceEnables querying and retrieving public design styles from the Driftless registry, including listing, searching styles, and fetching design markdown and tokens.MIT
TDQS
A3.8/5.0
Scored across 6 tools
Disambiguation4/5
Each tool targets a distinct action, and descriptions actively clarify the two closest pairs: search_styles (word-boundary keyword match) vs match_style (qualitative prose brief), and get_design_md (prose) vs get_style (raw JSON tokens). The boundaries are mostly clear, though a naive agent could still reach for search_styles when match_style is intended.
Naming Consistency4/5
All names share the refero_ prefix and snake_case with a verb_noun shape (search_styles, match_style, get_style, get_design_md, list_style_ids). refero_index_status is the one deviation (noun_noun rather than an action verb), but it is still readable and in the same convention.
Tool Count5/5
Six tools is well-scoped for a design-style discovery and rendering server, with each tool earning its place across the discovery, search, match, retrieve, and diagnostic phases.
Completeness4/5
The surface covers the full read lifecycle: discover ids (list_style_ids), search by text (search_styles), match by brief (match_style), retrieve as JSON (get_style) or prose (get_design_md), plus index diagnostics (index_status). Only minor gaps, such as filtered/paginated listing, remain and are workable given the sitemap-backed ids.
Maintenance
ActivityMaintained
ResponsivenessNo issues