Shipi18n vs Globalize.now
A side-by-side look at the Shipi18n and Globalize.now 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 Globalize.now 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 Shipi18n when
- You need dedicated capabilities in the Translation Services domain.
- You prefer a local stdio subprocess transport.
Choose Globalize.now 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 | ||
|---|---|---|
| Category | Translation Services | Translation Services |
| Quality signal | 44/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| 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 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Shipi18n | View Globalize.now |
Tools & capabilities
Shipi18n tools
No tool names declared yet. Check the project README from the listing page.
Globalize.now 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"
]
}
}
}
Globalize.now
{
"mcpServers": {
"globalize-now": {
"url": "https://api.globalize.now/mcp"
}
}
}
Frequently asked questions
Shipi18n is categorized under Translation Services and uses a local stdio subprocess. Globalize.now belongs to Translation Services and uses a remote HTTP/SSE transport. Pick Shipi18n for translation services work and Globalize.now 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.
Shipi18n has no declared pricing — check the project's own site. Globalize.now 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 shipi18n and globalize-now as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Shipi18n has a quality signal of 44/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Globalize.now has 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.