Raven MCP
Related Servers
Alternatives to Raven MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server that gives LLMs deep knowledge of design systems and tokens, enabling intelligent design evolution, token analysis, and designer-to-developer handoffs.378 npm2MIT
- AlicenseNot gradedqualityBmaintenanceAn 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
- AlicenseCqualityCmaintenanceA 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 gradedqualityCmaintenanceMCP 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.8 npmMIT
- FlicenseNot 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.-
TDQS
Scored across 111 tools
The long, heavily detailed descriptions help separate most tools, but there is real overlap at the set level: `audit` is an explicitly recommended catch-all for the two dozen individual `audit_*` tools, and `audit_screen`/`audit_ios_screen` are effectively the same check. With 111 tools, an agent must rely on lengthy prose rather than clear boundaries to avoid mis-selection.
The dominant convention is snake_case `verb_noun` (`get_`, `list_`, `create_`, `audit_`), so the set is readable overall. But it mixes in noun-first and domain-first forms such as `decision_*`, `gap_scan`, `talon_scan`, and `raven_reflect`, plus abbreviations like `audit_rn` and `audit_ios_a11y`, so the naming is not fully predictable.
111 selectable tools is far beyond any reasonable single MCP surface and well past the 50+ threshold. Many related operations, especially the roughly two dozen `audit_*` variants, could be grouped into a single parameterized tool or split into separate sub-servers. The breadth may be intentional, but this namespace is a heavy burden for agent selection.
The domain coverage is unusually comprehensive: reference capture, design-system token management, knowledge lookup, taste calibration, creative generation, decision graphs, and a wide range of audits all have lifecycle support. The main gaps are minor operational lifecycle operations, such as no apparent delete/cancel for creative generation jobs or brand profiles, and no universal update/delete path for every stored artifact.