UseVyre Context
Wire an agent to useVyre so generated UI uses correct props, variants, tokens, and avoids documented anti-patterns.
Overview
useVyre Context is a Build-phase MCP server that gives agents accurate useVyre props, variants, tokens, and anti-patterns while coding UI.
What is this MCP server?
- Surfaces valid props and variants per useVyre component
- Exposes design tokens for consistent styling in agent output
- Documents anti-patterns agents should avoid
- stdio npm package @usevyre/mcp-server (v1.0.3)
- Official docs at usevyre.com for AI tooling setup
- Server schema version 1.0.3
- Package @usevyre/mcp-server on npm
- stdio transport
What problem does it solve?
Agents hallucinate component APIs and ignore your design tokens, so useVyre screens need constant manual correction.
Who is it for?
Indie builders using useVyre who want Claude Code or Cursor to respect real component contracts during frontend work.
Skip if: Teams not on useVyre, or builders who only need generic CSS/React help without that library.
What do I get? / Deliverables
The agent can query canonical useVyre context so generated UI matches library rules and token usage out of the box.
- Queryable useVyre props, variants, and tokens inside the agent session
- Reduced invalid component usage in generated frontend code
- Aligned references to documented anti-patterns during implementation
Recommended MCP Servers
Journey fit
How it compares
Design-system context MCP, not a generic UI generator skill or Figma bridge.
Common Questions / FAQ
Who is UseVyre Context for?
Solo and small-team builders using the useVyre component library with AI agents that write frontend code.
When should I use UseVyre Context?
During Build when agents scaffold pages, forms, or dashboards that must use useVyre components correctly.
How do I add UseVyre Context to my agent?
Register the stdio MCP server using the @usevyre/mcp-server npm package per usevyre.com/docs/ai-tooling/mcp-server in Claude Code or Cursor.