MCP server

Wire UI MCP Server for Headless Components

The Wire UI MCP server lets an AI coding agent list, fetch and search headless, zero-CSS components and hooks across React, Vue and SolidJS from one catalog.

Run
npx @wire-ui/mcp
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the Wire UI MCP server?

Wire UI MCP is the official server for Wire UI, a headless component library with no built-in CSS, where interactive states expose through data attributes instead. It gives an agent eight tools to list and fetch components and hooks, get a decision tree for picking the right one, search documentation, and read setup instructions, all across React, Vue and SolidJS from a single framework parameter.

Wire UI is a headless, zero-CSS component library: components ship as compound primitives with no built-in styling, and interactive states show up as data attributes so any styling approach, Tailwind, CSS Modules or plain CSS, can be layered on top. The MCP server, published as @wire-ui/mcp, exposes that catalog to an AI coding agent.

The same server covers all three framework builds, React, Vue and SolidJS, through a single framework parameter on each tool, so an agent asks for a component once and gets the right implementation for the project it is working in.

What it changes in your workflow

  • list_components and get_component return a real component's categories, props and example code, so generated UI calls an existing primitive instead of an invented one.
  • get_decision_tree answers a scenario question, such as which component fits a given interaction, before the agent starts writing code.
  • search_docs finds a component, hook or decision tree by keyword without the agent switching to the documentation site.
  • get_exports_list returns every export in a package, components, hooks and TypeScript types, so an import statement matches the library's real public API.

Setup at a glance

Wire UI MCP server
Run commandnpx @wire-ui/mcp
Transportstdio, started by the client
Clients namedClaude Desktop, Claude Code, Cursor, VS Code, Windsurf, Trae
Framework parameterreact, solid or vue on every tool call, react by default

Who it is for

Best for

  • Teams that want full control over styling and only need the interaction and accessibility behavior from a library.
  • Projects that span more than one framework and want the same component catalog available in React, Vue and SolidJS.
  • Agents that need to pick the right primitive for a scenario through a decision tree instead of guessing from a component list.

Not for

  • If pre-styled, ready-to-ship components fit better than unstyled primitives, the shadcn MCP server fetches shadcn/ui component source and blocks directly.
  • When the target is a native SwiftUI app rather than a web framework, the ShipSwift MCP server supplies SwiftUI components and full-stack recipes instead.
  • Choose a styled React library when animated, accessible components are needed out of the box, the Lightswind UI MCP server installs over 160 ready React components.
  • Go with a Storybook tool when the deliverable is a documented screen rather than a bare component, the Story UI MCP server generates and inspects stories from a design system.

Use it with UiChemy

Wire UI supplies unstyled component behavior for a React, Vue or SolidJS codebase. UiChemy's Composer instead edits a WordPress page visually inside Elementor or Gutenberg, so the two apply to different parts of a stack.