TastePro
Related Servers
Alternatives to TastePro
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables coding agents building UI to fetch real product screens as inline images, pull typed design references, and find licensed fonts, icons, or animated icons when a visual question is unresolved. It also serves a bundled design workflow, command playbooks, and connection diagnostics.-
- AlicenseAqualityCmaintenanceMCP server that helps AI agents create UIs that don't look AI-generated by auditing components, refining copy, suggesting themes, and checking accessibility/contrast.8MIT
- FlicenseNot gradedqualityAmaintenanceConnects coding agents to a catalogue of real product screens so they can pull concrete UI references, fonts, icons, and the recorded design systems behind web screens when a visual question is open. It also serves bundled design-workflow documents, help, and connection diagnostics for grounding UI work in real products rather than generic templates.-
- FlicenseNot gradedqualityAmaintenanceAn MCP server that grounds coding-agent UI work in real product screens: it answers specific layout, state, or interaction questions with one to three real screen images, plus fonts, icons, and animated-icon materials with their recorded licenses, and returns full design references for web screens the agent has chosen. It also serves bundled design-workflow documents, playbook prompts, and connection diagnostics without requiring a token.-
- AlicenseNot gradedqualityDmaintenanceMCP 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.MIT
- AlicenseNot gradedqualityAmaintenanceThis MCP server gives coding agents real product screen references, design references, and font/icon materials from a curated catalogue so UI work is grounded in actual designs rather than generic templates. It also ships the skill's workflow documents and diagnostic tools, making them readable without a token.MIT
TDQS
Scored across 4 tools
Each tool occupies a distinct stage: taste_search discovers ids, taste_get retrieves full packs, taste_guidelines queries the rule corpus, and taste_audit validates HTML against those rules. The search/get split is explicitly documented (compact cards vs full pack), and guidelines vs audit is clearly separated as reference lookup versus enforcement.
All four tools share the taste_ prefix with short, predictable suffixes (search, get, guidelines, audit). The only minor deviation is 'guidelines', a noun rather than a verb, but it reads naturally as a resource retrieval alongside the other action names.
Four tools is a tight, well-scoped surface for a design-reference server: discovery, retrieval, rule lookup, and auditing. No tool looks redundant, and nothing feels padded or missing at the count level.
The set covers the full read-only lifecycle: find packs, fetch them, consult guidelines, and audit output against them, with sensible format and severity options. Minor gaps remain, such as no explicit tool to enumerate available kinds/domains or to list guideline ids without querying, but agents can work around these via search filters.