useVyre component context for AI agents — valid props, variants, anti-patterns, and design tokens.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-gapra-usevyre-context": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
useVyre component context for AI agents — valid props, variants, anti-patterns, and design tokens.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / design
Persistent memory using a knowledge graph
MCP server for accessing Figma plugin console logs and screenshots via Cloudflare Workers or local mode
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.
MCP Security Weekly
Get CVE alerts and security updates for io.github.gapra/usevyre-context and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
AI-native design system for humans and agents. Built on semantic CSS variables — no runtime magic, no hallucinations.
Most design systems were built for humans reading documentation. useVyre is built for both — every naming convention, token structure, and component API is designed so that AI coding agents (Claude, Cursor, Copilot, Windsurf) can generate correct, consistent UI without guessing.
| Problem | useVyre solution |
|---|---|
| AI hallucinates component props | Every component has an inline AI context block |
| AI uses raw color values | Semantic tokens replace all raw colors |
| AI generates inconsistent spacing | 4px grid enforced via spacing tokens |
| AI doesn't know valid variants | data-variant API is explicit and enumerated |
| Design system only works in one framework | CSS variables work everywhere |
Core
| Package | Version | Description |
|---|---|---|
@usevyre/tokens | DTCG-compliant design tokens → CSS variables, JS/TS, JSON | |
@usevyre/react | React + TypeScript components | |
@usevyre/vue | Vue 3 + TypeScript components | |
@usevyre/all · react-all · vue-all | — | Convenience meta-packages (tokens + components in one install) |
AI tooling
| Package | Version | Description |
|---|---|---|
@usevyre/ai-context | Machine-readable component schema for LLM system prompts | |
@usevyre/mcp-server | MCP server — gives agents live access to the component schema | |
@usevyre/eslint-plugin | Lints for invalid variants, raw colors, hallucinated props | |
@usevyre/validate-ai-context | CI check that the AI context stays in sync with components | |
@usevyre/prompt-templates | Ready-made prompts for generating UI with useVyre |
40+ production-ready components for React and Vue — buttons, forms (Input, Field, Radio, Checkbox, Select), overlays (Modal, Sheet, Popover, Tooltip), data (DataGrid, Table, Pagination), layout (Sidebar/AppLayout, Card, Tabs), and richer pieces like Kanban, Conversation (chat), DateRangePicker, and a zero-dependency RichTextEditor — plus more on the way.
Every component ships with an inline AI-context block, a machine-readable schema entry, and documented anti-patterns.
Browse the full list with live demos → usevyre.com/docs/components
# React
npm install @usevyre/tokens @usevyre/react
# Vue 3
npm install @usevyre/t
... [View full README on GitHub](https://github.com/gapra/usevyre#readme)