shadcn-ui-mcp-server and daisyui-mcp
These are competitors—both provide MCP servers that give LLMs context about UI component libraries (shadcn/ui vs DaisyUI), allowing developers to choose one based on their preferred component framework rather than using them together.
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 daisyui-mcp
birdseyevue/daisyui-mcp
🌼 A token-friendly local MCP server for DaisyUI component documentation using their public llms.txt.
Exposes two MCP tools (`list_components` and `get_component`) that fetch DaisyUI docs from their public llms.txt and store them locally as editable markdown files. Built on FastMCP with stdio transport, it integrates directly into AI assistant configurations (Claude, etc.) to enable real-time component lookups without embedding full documentation in prompts. Supports both native Python execution and Docker deployment with hot-reloadable component definitions.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work