MCP server for accessing UI components, documentation, demos, and Radix component information from the vibeus design system
6 tools with clear names and basic schemas. Most descriptions are present but lack actionable detail and LLM optimization. Input schemas are properly typed with parameter descriptions, but output schemas are not documented. No error handling guidance or recovery strategies. Tool naming follows verb_noun pattern well (get_, list_), but descriptions are generic and lack WHEN to use guidance. Parameters are mostly well-described but missing constraints (enums, formats, ranges). Security is solid (no credentials exposed). Composition is sound, each tool does one thing. Typical community server: functional but needs refinement for production LLM use.
Get the .tsx example code from the `apps/docs/demo/` directory (referenced by <DemoRenderer> in mdx).
Get the .mdx source file for a component. This file contains usage examples and manually maintained Props API tables.
Get the content of package.json from a package or the monorepo root.
Read the .mdx source file content for a Radix component from the `website/data/primitives/docs/components` directory.
Get the .tsx source code for a component based on its base file name (module path).
Get a list of all available component base names in the @vibeus/ui library (e.g., "button", "dialog").
Output schemas not documented. Tool definitions show input schemas and descriptions but do NOT document what each tool returns. LLMs cannot plan downstream calls or extract correct fields without return types.
Descriptions lack actionable guidance. Most descriptions state WHAT the tool does but omit WHEN to use it, prerequisites, or how it fits into a workflow. E.g., 'Get the .tsx source code for a component' does not explain: is this for code generation? Inspection? Documentation? Does the agent need to call listUIComponents first?
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 60 | 2025-06-18+ | v2 |
| 2026-03-09 | F | 47 | - | v1 |
Parameter descriptions exist but lack format constraints. E.g., 'componentName' is described as 'The module path of the component' but does NOT specify: Is it case-sensitive? Are hyphens valid? Can it include paths like 'dialog/form'? Does it need file extensions? Ambiguity forces LLMs to guess.
No error handling guidance. Tool definitions do not specify: What happens if a component name is invalid? Should the agent call listUIComponents to discover valid names? If a file does not exist, should it retry? Error responses are likely unstructured or missing recovery hints.
Tool annotations missing. No tool declares whether it is read-only, destructive, or idempotent. LLMs cannot infer retry safety, tools may be retried unnecessarily or not retried when safe.