Origin Ui MCP Server

MCP server for OriginUI components with search and installation capabilities

Local serverstdioTypeScript

What is the Origin Ui MCP MCP server?

Origin Ui MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for OriginUI components with search and installation capabilities.

What you get

A Model Context Protocol (MCP) server that provides access to OriginUI components, enabling Claude Code agents to search, browse, and install OriginUI components seamlessly.

  • Component Search — Search components by name, category, or tags
  • Component Details — Get comprehensive information about specific components
  • Installation Commands — Generate proper pnpm dlx shadcn@latest add commands
  • Visual Previews — Get component screenshots and visual descriptions to assess fit
  • Component Preview — View styling information and usage examples
  • Category Filtering — Browse components by category (buttons, inputs, forms, etc.)

What the assistant can call

Once Origin Ui MCP is connected, these are the calls the assistant has available:

  • search_components — The search_components tool exposed by this server
  • get_component_details — The get_component_details tool exposed by this server
  • list_components — The list_components tool exposed by this server
  • get_install_command — The get_install_command tool exposed by this server
  • get_component_preview — Get component preview with styling information and usage examples
  • get_component_screenshot — Get component visual preview to help assess if it fits your project

Setting it up

Installation goes through your MCP client rather than a global install: point it at npm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Origin Ui MCP's toolset — search_components, get_component_details, list_components and 3 more — is a fair guide to whether it matches your workflow. It is maintained by kelvinchng; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Origin Ui MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the origin ui mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
search_componentsThe search_components tool exposed by this server.
get_component_detailsThe get_component_details tool exposed by this server.
list_componentsThe list_components tool exposed by this server.
get_install_commandThe get_install_command tool exposed by this server.
get_component_previewGet component preview with styling information and usage examples.
get_component_screenshotGet component visual preview to help assess if it fits your project.

How to install the Origin Ui MCP MCP server

{
  "mcpServers": {
    "origin-ui": {
      "command": "npx",
      "args": ["--yes", "github:kelvinchng/origin-ui-mcp"],
      "env": {}
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Origin Ui MCP to search components.
  • Use Origin Ui MCP to get component details.
  • Use Origin Ui MCP to list components.

Frequently asked questions

It connects Origin Ui MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (search_components, get_component_details, list_components, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Origin Ui MCP directly.