Shadcn Ui MCP Server vs Locize
A side-by-side look at the Shadcn Ui MCP Server and Locize MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
LocizeTranslation Services · Remote HTTP/SSELocize MCP server: read/write translations, publish versions, manage branches from AI assistants.42FairAuth: not declaredVerdict: choose Shadcn Ui MCP Server for developer tools work as a local process; choose Locize for translation services over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
LChoose Locize when
- You need dedicated capabilities in the Translation Services domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L Locize | |
|---|---|---|
| Category | Developer Tools | Translation Services |
| Quality signal | 72/100 · Great | 42/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | MCP_TRANSPORT_MODEMCP_PORTMCP_HOSTMCP_CORS_ORIGINSGITHUB_PERSONAL_ACCESS_TOKENUI_LIBRARY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3,068 | — |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 10 | Not listed |
| Full listing | View Shadcn Ui MCP Server | View Locize |
Tools & capabilities
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
Locize tools
No tool names declared yet. Check the project README from the listing page.
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.
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"
}
}
}
}
Locize
{
"mcpServers": {
"locize": {
"url": "https://www.locize.com/docs/integration/mcp"
}
}
}
Frequently asked questions
Shadcn Ui MCP Server is categorized under Developer Tools and uses a local stdio subprocess. Locize belongs to Translation Services and uses a remote HTTP/SSE transport. Pick Shadcn Ui MCP Server for developer tools work and Locize for translation services.
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.
Shadcn Ui MCP Server is listed as free. Auth: api key required. Locize has no declared pricing — check the project's own site. 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 jpisnice-shadcn-ui-mcp-server and locize as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Shadcn Ui MCP Server has a quality signal of 72/100 (Great) with 3 views, 0 installs and 3,068 GitHub stars. Locize has 42/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.