useVyre Context MCP Server

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. It runs locally over stdio via the published package.

People connecting design tools to Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-08-04 · ★ 7 · #43 OF 74 MAINTAINED DESIGN · VERIFIED 2026-08-25

MIT · TypeScript servers · how we verify → /methodology

01 · Install useVyre Context

Claude Code

claude mcp add gapra-usevyre -- npx -y @usevyre/mcp-server

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "gapra-usevyre": {
      "command": "npx",
      "args": [
        "-y",
        "@usevyre/mcp-server"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

npm package @usevyre/mcp-server - the @usevyre scope differs from the repo owner (gapra); confirm it's the project's official package

registry namespace io.github.gapra is GitHub-verified and matches the repo owner

03 · What useVyre Context can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v1.3.0 · 2026-05-18

1.3.0 · Expand and fix the Stack / Grid / Box layout primitives. · Bug fix (Grid): when a style prop was passed to <Grid>, the user's style object overwrote the internal --vyre-grid-columns custom property, so columns…

v1.2.0 · 2026-05-17

1.2.0 · Add Item, DateRangePicker, Kanban, Conversation; Calendar gains defaultMonth · Item - composable row primitive for list / settings / notification rows, denser than Card. Sub-components: ItemGroup (separated…

v1.0.0 · 2026-05-10

useVyre v1.0.0 · The first stable release of useVyre - an AI-native design system for React and Vue, built to eliminate AI hallucinations in frontend development. · --- · What's included · 30 components - all…

04 · Who maintains useVyre Context

useVyre Context is maintained by gapra. It's the only MCP server we track from this author; the repo dates to May 2026.

05 · Facts

category
design - ranked #43 of 74 actively-maintained design servers as of 2026-08-25.
registry
io.github.gapra/usevyre-context (active, first published 2026-05-13 · 2 versions)
packages
npm:@usevyre/mcp-server

06 · useVyre Context FAQ

What is useVyre Context?

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. It runs locally over stdio via the published package.

Is useVyre Context still maintained?

Yes - as of 2026-08-25, its last commit was 2026-08-04. We re-verify nightly.

How do I install useVyre Context?

Run `npx -y @usevyre/mcp-server`. You can also paste the ready-made client config above.

Does useVyre Context run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to useVyre Context