A
licenseNot graded
qualityD
maintenanceEnables AI coding environments to enforce engineering governance through MCP tools and resources for init, check, route, and review workflows.
10 npm
2
MIT
tidy-core
by rominak
Related Servers
Alternatives to tidy-core
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to access a governed, versioned design style specification through MCP, including deterministic checks, proposal review workflows, and generated CSS, JSON, and TypeScript artifacts.Apache 2.0
- AlicenseAqualityCmaintenanceEnables users to turn ideas or PRDs into component selections and architecture designs, audit existing projects with static scans, and manage long-running planning/auditing tasks with caching, cancellation, budget tracking, and checkpoint resume via MCP tools.7MIT
- AlicenseNot gradedqualityCmaintenanceMCP 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
- FlicenseNot gradedqualityCmaintenanceProvides governed MCP tools for a controlled, AI-assisted asset-change pipeline, featuring natural-language requests, mandatory approvals, execution-time revalidation, and complete audit.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to apply organization-specific AI product governance policies through read-only tools, prompts, and resources, including risk-tier scoring, unit-economics calculations, and gated governance workflows.MIT
TDQS
B3.2/5.0
Scored across 13 tools
Disambiguation4/5
Tools like tidy_plan and tidy_apply have clear separation (read vs. execute), and tidy_status/tidy_target handle connection vs. targeting. However, some tools like tidy_health, tidy_impact, and tidy_cleanup all involve analysis of the design system, and their distinct purposes might not be immediately obvious without reading descriptions closely, though descriptions do help.
Naming Consistency5/5
All tools use the pattern 'tidy_' prefix followed by a lowercase verb or noun in snake_case, e.g., tidy_status, tidy_target, tidy_plan, tidy_apply. This is perfectly consistent and predictable.
Tool Count4/5
13 tools is within the recommended range. However, 8 of them are marked as not implemented yet, which might make the server feel thin in terms of actual functionality, but the planned surface is of appropriate size for a comprehensive design system management toolkit.
Completeness3/5
The implemented tools cover status, targeting, context, planning, and applying changes, which are core operations. However, many permanent capabilities like adoption, drift, health, impact, cleanup, decisions, and gating are not yet implemented, leaving notable gaps in the intended functionality.
Maintenance
ActivitySlowing
ResponsivenessNo issues