Shipi18n vs Tolgee
A side-by-side look at the Shipi18n and Tolgee MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Shipi18n for translation services work as a local process; choose Tolgee for translation services. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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 | 44/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | 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 | 4,139 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Shipi18n | View Tolgee |
Tools & capabilities
Shipi18n tools
No tool names declared yet. Check the project README from the listing page.
Tolgee 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.
Shipi18n
{
"mcpServers": {
"shipi18n": {
"command": "npx",
"args": [
"-y",
"@shipi18n/cli"
]
}
}
}
Tolgee
No confirmed install command for Tolgee yet — follow the setup steps linked from its listing page rather than a guessed package name.