Weblate MCP vs Shipi18n
A side-by-side look at the Weblate MCP and Shipi18n MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Weblate MCP for translation services work as a local process; 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?
Choose Weblate MCP when
- You need dedicated capabilities in the Translation Services domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
WEBLATE_API_URL, WEBLATE_API_TOKEN.
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 | ||
|---|---|---|
| Category | Translation Services | Translation Services |
| Quality signal | 59/100 · Good | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | WEBLATE_API_URLWEBLATE_API_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 23 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Weblate MCP | View Shipi18n |
Tools & capabilities
Weblate MCP 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.
Weblate MCP
{
"mcpServers": {
"mmntm-weblate-mcp": {
"command": "npx",
"args": [
"-y",
"-",
"no"
],
"env": {
"WEBLATE_API_URL": "YOUR_WEBLATE_API_URL_HERE",
"WEBLATE_API_TOKEN": "YOUR_WEBLATE_API_TOKEN_HERE"
}
}
}
}
Shipi18n
{
"mcpServers": {
"shipi18n": {
"command": "npx",
"args": [
"-y",
"@shipi18n/cli"
]
}
}
}
Frequently asked questions
Weblate MCP is categorized under Translation Services and uses a local stdio subprocess. Shipi18n belongs to Translation Services and uses a local stdio subprocess. Pick Weblate MCP 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.
Weblate MCP is listed as free. Auth: api key required. 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 mmntm-weblate-mcp and shipi18n as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Weblate MCP has a quality signal of 59/100 (Good) with 3 views, 0 installs and 23 GitHub stars. Shipi18n has 44/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.