useVyre Context

io.github.gapraPublished by GitHub account gaprav1.0.3Updated Oct 24, 2026

useVyre component context for AI agents — valid props, variants, anti-patterns, and design tokens.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A local MCP server that gives assistants useVyre component context: valid props, variants, design tokens and anti-patterns for generating UI code.

What you can do
Look up a component's full context, including props, variants, examples and anti-patterns, or fetch the entire context block for all components and tokens at once. Retrieve all valid prop names and values for a component, and validate a specific prop value before generating code. Find a suitable component for a described use case, and look up design tokens by name or category. List known hallucination patterns, optionally filtered by component, and check the package version and context validity.
When to use it
Useful when an assistant writes or reviews UI code against the useVyre component library and needs accurate prop names, variants and tokens instead of guessing. Also helpful for checking a prop value or picking the right component before generating markup.
Requirements
Runs as a local process over stdio, launched with npx from the npm package @usevyre/mcp-server, so Node.js and network access for the package are needed. The README shows configuration in the Claude Desktop config file. No authentication, environment variables or headers are declared.
Before you install
The README instructs adding the server to the Claude Desktop configuration and restarting the app; review the package before running it, since npx fetches and executes it locally. No credentials, payments or write actions are shown in the input.

Installation

In SourceWeft

  1. Open useVyre Context in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@usevyre/mcp-server

MCP (Model Context Protocol) server for useVyre — gives Claude Desktop and other MCP clients real-time access to component context, valid props, and anti-patterns.

[npm] [MIT License]

Setup — Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

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

Restart Claude Desktop. The useVyre tools will appear in the tools panel.

Available tools

ToolDescription
get_component_infoFull context for a component — props, variants, anti-patterns, examples
get_valid_propsAll valid prop names and values for a component
check_valid_prop_valueValidate a specific prop value before generating code
suggest_componentFind the right component for a use case
get_token_infoLook up a design token by name or category
get_full_contextEntire AI context block (all components + tokens)
get_anti_patternsAll known hallucination patterns, optionally filtered by component
get_version_infoPackage version and context validity information

Example prompts

"What are the valid variants for the Button component?"→ get_valid_props({ component: "Button" })
"Is variant='error' valid on Alert?"→ check_valid_prop_value({ component: "Alert", prop: "variant", value: "error" })
"What component should I use for a search box?"→ suggest_component({ useCase: "search box with keyboard navigation" })

Docs

usevyre.com/docs/ai-tooling/mcp-server

Source: packages/mcp-server/README.md at commit d7791d0

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts