Locize vs Shipi18n
A side-by-side look at the Locize and Shipi18n 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 Locize for translation services work over a hosted endpoint; choose Shipi18n for translation services as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
LChoose Locize when
- You need dedicated capabilities in the Translation Services domain.
- You prefer a remote HTTP/SSE transport.
Choose Shipi18n when
- You need dedicated capabilities in the Translation Services domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L Locize | |
|---|---|---|
| Category | Translation Services | Translation Services |
| Quality signal | 42/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Locize | View Shipi18n |
Tools & capabilities
Locize tools
No tool names declared yet. Check the project README from the listing page.
Shipi18n 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.
Locize
{
"mcpServers": {
"locize": {
"url": "https://www.locize.com/docs/integration/mcp"
}
}
}
Shipi18n
{
"mcpServers": {
"shipi18n": {
"command": "npx",
"args": [
"-y",
"@shipi18n/cli"
]
}
}
}
Frequently asked questions
Locize is categorized under Translation Services and uses a remote HTTP/SSE transport. Shipi18n belongs to Translation Services and uses a local stdio subprocess. Pick Locize for translation services work and Shipi18n 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.
Locize has no declared pricing — check the project's own site. Shipi18n 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 locize and shipi18n as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Locize has a quality signal of 42/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Shipi18n has 44/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.