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 command | npx @wire-ui/mcp |
| Transport | stdio, started by the client |
| Clients named | Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Trae |
| Framework parameter | react, 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.
Connect Wire UI MCP Server for Headless Components to your AI client
npx @wire-ui/mcpAdd the server to your client
Put the config above in your MCP client's settings. Claude Desktop on macOS, Cursor, VS Code, Windsurf and Trae each take the same entry in their own config location.
Restart the client
Restart so the client starts the server over stdio through npx.
Pick a framework
Pass react, solid or vue as the framework parameter on a tool call; react is the default when it is left out.
List what is available
Ask the agent to call list_components or list_hooks for the chosen framework to confirm it returns real Wire UI names.
Fetch a component
Ask the agent to call get_component for a named component to read its props and example code.
Client configuration
{
"mcpServers": {
"wire-ui": {
"command": "npx",
"args": ["@wire-ui/mcp"]
}
}
}Endpoints and ports
@wire-ui/mcpPublished npm package that the npx command runs.wire-ui.comFull component, hook and setup documentation for all three frameworks.What you can do with it
- Headless, zero CSSComponents ship with no built-in styling; interactive states appear as data attributes for Tailwind, CSS Modules or plain CSS to style.
- Three frameworks, one catalogEvery tool takes a framework parameter of react, solid or vue, so the same questions work across all three implementations.
- Scenario-based pickingget_decision_tree answers which component fits a given interaction instead of requiring the agent to browse the whole catalog.
- Real props and examplesget_component and get_hook return actual props, signatures and example code rather than a generated guess.
- Keyword documentation searchsearch_docs finds a relevant component, hook or decision tree by keyword without leaving the agent conversation.
- Full export listingget_exports_list returns every component, hook and TypeScript type a package exports, keeping import statements accurate.
- Setup guidanceget_installation_guide returns framework-specific dependency information and setup steps for the chosen target.
Tools it exposes
list_components
Lists Wire UI components for a chosen framework with their categories and descriptions.
get_component
Returns full detail on one component, including its props and example code.
list_hooks
Lists the hooks, primitives or composables available for a chosen framework.
get_hook
Returns one hook's signature and example code.
get_decision_tree
Returns a decision tree to help pick the right component for a given scenario.
search_docs
Searches components, hooks and decision trees by keyword.
get_installation_guide
Returns setup instructions and framework-specific dependency information.
get_exports_list
Lists every export from a Wire UI package, including components, hooks and TypeScript types.
Frequently asked questions
What is the Wire UI MCP server?
It is the official MCP server for Wire UI, a headless component library with no built-in CSS. It gives an AI coding agent eight tools to list, fetch and search components and hooks across React, Vue and SolidJS.
How do I install the Wire UI MCP server?
Add an entry to your MCP client's configuration that runs npx @wire-ui/mcp as the command, then restart the client. The same entry works for Claude Desktop, Claude Code, Cursor, VS Code, Windsurf and Trae with their own config locations.
Does it support more than one framework?
Yes. Every tool accepts a framework parameter of react, solid or vue, with react as the default, so the same server answers questions for all three Wire UI implementations without a separate install for each.
What does headless, zero CSS mean here?
Components ship with no built-in visual styling. Interactive states, such as open, hover or disabled, show up as data attributes instead, so a project styles them with Tailwind, CSS Modules or plain CSS rather than overriding preset styles.
How do I pick the right component for a scenario?
Call get_decision_tree with a description of the interaction needed. It returns a decision tree that narrows down to the right Wire UI component instead of requiring a manual read through the full component list.
Can it tell me everything a package exports?
Yes. The get_exports_list tool returns every export from a Wire UI package, covering components, hooks or composables, and TypeScript types, so generated import statements match the library's real public API.
Which AI coding agents and editors work with it?
The project names Claude Desktop, Claude Code, Cursor, VS Code, Windsurf and Trae as supported clients. Any other MCP-compatible client that can run an npx command over stdio should connect the same way.


