A side-by-side look at the Shadcn Ui MCP Server and Vibie MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Shadcn Ui MCP Server for developer tools work as a local process; choose Vibie MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
MCP_TRANSPORT_MODE, MCP_PORT, MCP_HOST, MCP_CORS_ORIGINS, GITHUB_PERSONAL_ACCESS_TOKEN, UI_LIBRARY.get_component, get_component_demo, list_components.VIBIE_API_BASE.vibie_create_site, vibie_update_site, vibie_list_sites.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 72/100 · Great | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | OAuth 2.0 |
| Pricing | Free | Free |
| Required env vars | MCP_TRANSPORT_MODEMCP_PORTMCP_HOSTMCP_CORS_ORIGINSGITHUB_PERSONAL_ACCESS_TOKENUI_LIBRARY | VIBIE_API_BASE |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3,041 | 1 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 10 | 4 |
| Full listing | View Shadcn Ui MCP Server | View Vibie MCP |
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 themevibie_create_siteCreate a NEW Vibie site by uploading a local folder. Use this when the user wants to publish a brand new site, or when no .vibie/site.json marker exists in the folder. Vibie hosts static HTML/CSS/JS at a permanent URL like my-site-a3f9.vibie.page. Auto-creates a .vibie/site.json marker in the folder for future updates.vibie_update_siteUpdate an existing Vibie site with new content from a local folder. Use this when the user wants to re-deploy or push changes to an already-published site. If .vibie/site.json marker exists in the folder, the slug is read automatically; otherwise pass slug explicitly. Same URL, new content.vibie_list_sitesList all sites owned by the current Vibie user. Returns slug, display name, category, URL, visibility, and last update time. Use this to discover what sites the user already has, e.g. before update.vibie_get_siteGet metadata for a single Vibie site by slug. Returns name, category, URL, visibility, like count, timestamps.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.
{
"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"
}
}
}
}
{
"mcpServers": {
"shdomi8599-vibie-mcp": {
"command": "npx",
"args": [
"-y",
"vibie-mcp"
],
"env": {
"VIBIE_API_BASE": "YOUR_VIBIE_API_BASE_HERE"
}
}
}
}