vibecraft-mcp
Related Servers
Alternatives to vibecraft-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to inspect a project's design tokens and component catalog, audit React/Tailwind files against seven static UI quality rules, score overall UI health, and apply auto-fixes that are re-audited and reverted on regression. It works both locally over filesystem access and remotely on raw TSX/JSX or CSS snippets passed directly as strings.-
- AlicenseAqualityCmaintenanceProvides conversational, actionable accessibility testing for AI agents, including auditing, prioritization, and code-level fixes.227 npmMIT
- AlicenseNot gradedqualityBmaintenanceDeterministic AI code review with audit records, providing stack-specific rulesets and governance for coding agents.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to score live URLs against a 40-check design contract, validate DTCG tokens and Lottie animations, audit accessibility, and retrieve design-system contracts, catalogs, and review rubrics.4 npmMIT
- FlicenseNot gradedqualityCmaintenanceGives AI coding assistants live, structured access to running apps' state and UI elements, enabling real-time verification and interaction across web, mobile, and desktop.36-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to run deterministic API validation and UI DOM checks, verifying HTTP status codes, JSON schema fields, and page elements with programmatic proof instead of LLM guesswork.MIT
TDQS
Scored across 7 tools
Tools are mostly distinct: audits target performance vs UX compliance, and get_component_code/search_ui_components form a clear pair. The only real ambiguity is between get_layout_blueprint and get_ux_guidelines, since both reference NN/g IA and design guidance.
All seven tools follow the same lowercase snake_case verb_noun convention: audit_, get_, search_. No mixed styles or vague generic verbs.
Seven tools is well-scoped for a design/UX assistant: guidance retrieval, component discovery/code retrieval, token retrieval, and two complementary audit paths. Each tool has a clear role.
The set covers the core workflow of a design-system copilot: retrieve guidelines/layouts/tokens, find and fetch components, and audit both UX compliance and system performance. No obvious dead ends or missing lifecycle steps for this domain.