Raven MCP
Related Servers
Alternatives to Raven MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that gives LLMs deep knowledge of design systems and tokens, enabling intelligent design evolution, token analysis, and designer-to-developer handoffs.3713 npm2MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI assistants structured access to a design system's tokens, components, guidelines, and patterns, enabling them to read, lint, and author design system data.1MIT
- AlicenseBqualityDmaintenanceAn MCP server that drives Anthropic's Claude Design from agentic coding CLIs, providing tools to create, generate, iterate, and export design systems without a browser.32MIT
- AlicenseCqualityDmaintenanceA comprehensive MCP server that enables Claude to read, create, edit, and generate code from Figma designs. Supports design tokens, code generation to multiple frameworks, and accessibility checks.1004MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for design decisions during a build, providing live UI/animation library docs (via llms.txt) and a curated knowledge base of UX laws and UI conventions. It enables agents to look up real component APIs and apply design best practices, running locally via stdio or hosted on Vercel.6 npmMIT
- 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
TDQS
Scored across 115 tools
The set contains many overlapping audit and evaluation tools, including `audit`, `audit_page`, `score_page`, `audit_url`, `talon_scan`, `design_gauntlet`, and numerous platform-specific audit variants. The `audit` description explicitly says to use it instead of choosing individual `audit_*` tools, which admits redundancy and makes tool selection confusing for an agent.
Almost all tools use readable snake_case and most follow a verb_noun pattern, such as `get_design_system`, `create_generation_job`, and `audit_contrast`. There are minor namespace inconsistencies (`raven_register`, `decision_*`, bare `audit`) but no chaotic mixed casing.
At 115 tools, this is far beyond a well-scoped surface and creates an extreme mismatch for an agent using the server as a coherent toolkit. Many tools appear to be layered alternatives or niche variants that should be discoverable through fewer entry points.
The surface is extremely broad, covering audits, design systems, taste calibration, references, motion, creative generation, and decision tracking. Some resource lifecycles lack obvious delete/update operations, but the major domains are well represented with only minor gaps.