OriginUI MCP Server

Related Servers

Alternatives to OriginUI MCP Server

No user-submitted related servers found.

Related Servers

shadcn-ui MCP Server
Documentation Access Developer Tools
totodev999
A
license
A
quality
D
maintenance
Provides reference information for shadcn/ui components through a Model Context Protocol server that helps AI assistants access component documentation and examples.
Updated a year ago (2025-06-09 01:00 UTC)
4
372 npm
MIT
ui-registry-mcp
Developer Tools Coding Agents
mrityunjay-tiwari
A
license
A
quality
B
maintenance
Provides coding agents live access to shadcn-style component registries, enabling them to search, compare, and fetch real component source code for UI composition.
Updated 2 months ago (2026-07-13 09:29 UTC)
5
61 npm
5
MIT
shadcn MCP Server
Developer Tools Documentation Access
magnusrodseth
F
license
A
quality
D
maintenance
Provides AI assistants with direct access to shadcn/ui components and blocks, enabling real-time fetching of component source code, documentation, and implementation examples.
Updated a year ago (2025-07-22 10:55 UTC)
4
8 npm
4
-
shadcn MCP Server
Developer Tools Code Analysis Documentation Access
krutikkkkkkkkk
A
license
Not graded
quality
D
maintenance
Enables AI assistants to discover, install, and generate code examples for shadcn/ui components, providing installation commands and usage examples for 37+ React UI components.
Updated a year ago (2025-08-06 16:50 UTC)
MIT
shadcn-ui MCP Server
Documentation Access Developer Tools
ymadd
A
license
A
quality
D
maintenance
Helps AI assistants access shadcn/ui component documentation and examples through a TypeScript-based MCP server that provides reference information for component details, usage examples, and search capabilities.
Updated a year ago (2025-04-14 06:54 UTC)
4
372 npm
60
MIT
shadcn-ui-mcp-server
Developer Tools Documentation Access
EzequielPereirae
A
license
A
quality
D
maintenance
Provides AI assistants with comprehensive access to shadcn/ui v4 components, blocks, demos, and metadata across React, Svelte, Vue, and React Native, enabling efficient component integration and code generation.
Updated a month ago (2026-08-19 23:53 UTC)
2
10
1,712 npm
MIT

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored 2026-04-18 06:35 across 7 tools

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity: list_components and search_components handle discovery, get_component_details/preview/screenshot provide different types of component information, get_install_command gives installation instructions, and get_registry_stats offers registry-level data. The descriptions make it easy to differentiate between tools like get_component_details (detailed info) and get_component_preview (styling/usage).

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case throughout (e.g., get_component_details, list_components, search_components). The naming is predictable and readable, using clear verbs like 'get', 'list', and 'search' consistently across the toolset.

Tool Count5/5

With 7 tools, this server is well-scoped for its purpose of managing a UI component registry. Each tool earns its place by covering distinct aspects: discovery (list/search), component inspection (details/preview/screenshot), installation (install_command), and registry analytics (stats). This count is neither too thin nor overwhelming.

Completeness4/5

The tool surface provides comprehensive coverage for the domain of a UI component registry, including discovery, inspection, and installation. Minor gaps exist, such as no tools for managing components (e.g., create/update/delete) or user-specific actions (e.g., favorites), but agents can work around this for core workflows like finding and using components.