Cellarion vs Shadcn Ui MCP Server
A side-by-side look at the Cellarion and Shadcn Ui MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cellarion for other tools and integrations work over a hosted endpoint; choose Shadcn Ui MCP Server for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cellarion when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
JWT_SECRET, MEILI_MASTER_KEY.
Choose Shadcn Ui MCP Server when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
MCP_TRANSPORT_MODE, MCP_PORT, MCP_HOST, MCP_CORS_ORIGINS, GITHUB_PERSONAL_ACCESS_TOKEN, UI_LIBRARY. - You want tools like
get_component, get_component_demo, list_components.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Developer Tools |
| Quality signal | 44/100 · Fair | 72/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | JWT_SECRETMEILI_MASTER_KEY | MCP_TRANSPORT_MODEMCP_PORTMCP_HOSTMCP_CORS_ORIGINSGITHUB_PERSONAL_ACCESS_TOKENUI_LIBRARY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 26 | 3,068 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 10 |
| Full listing | View Cellarion | View Shadcn Ui MCP Server |
Tools & capabilities
Cellarion tools
No tool names declared yet. Check the project README from the listing page.
Shadcn Ui MCP Server tools 10
get_componentGet the source code for a specific shadcn/ui v4 componentget_component_demoGet demo code illustrating how a shadcn/ui v4 component should be usedlist_componentsGet all available shadcn/ui v4 componentsget_component_metadataGet metadata for a specific shadcn/ui v4 componentget_directory_structureGet the directory structure of the shadcn-ui v4 repositoryget_blockGet source code for a specific shadcn/ui v4 block (e.g., calendar-01, dashboard-01)list_blocksGet all available shadcn/ui v4 blocks with categorizationapply_themeApply a TweakCN theme preset to the projectlist_themesList available tweakcn themesget_themeGet details of a specific tweakcn theme
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Cellarion
{
"mcpServers": {
"cellarion": {
"url": "https://cellarion.app/api/mcp"
}
}
}
Shadcn Ui MCP Server
{
"mcpServers": {
"jpisnice-shadcn-ui-mcp-server": {
"command": "npx",
"args": [
"-y",
"@jpisnice/shadcn-ui-mcp-server"
],
"env": {
"MCP_TRANSPORT_MODE": "YOUR_MCP_TRANSPORT_MODE_HERE",
"MCP_PORT": "YOUR_MCP_PORT_HERE",
"MCP_HOST": "YOUR_MCP_HOST_HERE",
"MCP_CORS_ORIGINS": "YOUR_MCP_CORS_ORIGINS_HERE",
"GITHUB_PERSONAL_ACCESS_TOKEN": "YOUR_GITHUB_PERSONAL_ACCESS_TOKEN_HERE",
"UI_LIBRARY": "YOUR_UI_LIBRARY_HERE"
}
}
}
}
Frequently asked questions
Cellarion is categorized under Other Tools and Integrations and uses a remote HTTP/SSE transport. Shadcn Ui MCP Server belongs to Developer Tools and uses a local stdio subprocess. Pick Cellarion for other tools and integrations work and Shadcn Ui MCP Server for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Cellarion has no declared pricing — check the project's own site. Shadcn Ui MCP Server is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cellarion and jpisnice-shadcn-ui-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cellarion has a quality signal of 44/100 (Fair) with 2 views, 0 installs and 26 GitHub stars. Shadcn Ui MCP Server has 72/100 (Great) with 3 views, 0 installs and 3,068 GitHub stars.