shadcn-ui-mcp-server and webmcp-react
These are complementary tools: shadcn-ui-mcp-server provides LLM context about UI component libraries via MCP, while webmcp-react enables React applications to expose their functionality as MCP tools, allowing bidirectional integration between LLMs and React apps.
About shadcn-ui-mcp-server
Jpisnice/shadcn-ui-mcp-server
A mcp server to allow LLMS gain context about shadcn ui component structure,usage and installation,compaitable with react,svelte 5,vue & React Native
Implements the Model Context Protocol (MCP) with direct GitHub API access to shadcn/ui repositories, providing AI assistants with real-time component source code, demos, and block implementations. Supports dual transport modes—stdio for CLI and SSE for HTTP-based multi-client deployments—with intelligent caching and configurable GitHub token authentication for rate limit optimization. Enables framework-agnostic component integration with switchable primitive libraries (Radix UI or Base UI) and one-click installation via `.mcpb` bundles for Claude Desktop.
About webmcp-react
MCPCat/webmcp-react
React hooks for exposing your app's functionality as WebMCP tools - transport-agnostic, SSR-safe, Strict Mode safe, W3C spec-aligned
Provides Zod-first tool definitions with automatic type inference, plus a lightweight polyfill for environments lacking native `navigator.modelContext` support. Integrates with the emerging WebMCP standard to expose browser-based tools to AI agents via desktop MCP clients (Claude, Cursor) through an optional Chrome extension bridge, with dynamic tool registration tied to React component lifecycle.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work