MachineTranslation.com MCP vs Shipi18n
A side-by-side look at the MachineTranslation.com 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 MachineTranslation.com MCP 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?
Choose MachineTranslation.com MCP when
- You need dedicated capabilities in the Translation Services domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
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 | 64/100 · Good | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 4 views 1 installs 1 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MachineTranslation.com MCP | View Shipi18n |
Tools & capabilities
MachineTranslation.com 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.
MachineTranslation.com MCP
{
"mcpServers": {
"machinetranslation-com-mcp": {
"url": "https://www.machinetranslation.com/mcp"
}
}
}
Shipi18n
{
"mcpServers": {
"shipi18n": {
"command": "npx",
"args": [
"-y",
"@shipi18n/cli"
]
}
}
}
Frequently asked questions
MachineTranslation.com MCP is categorized under Translation Services and uses a remote HTTP/SSE transport. Shipi18n belongs to Translation Services and uses a local stdio subprocess. Pick MachineTranslation.com 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.
MachineTranslation.com MCP is listed as a paid service. Auth: oauth 2.0. 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 machinetranslation-com-mcp and shipi18n as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MachineTranslation.com MCP has a quality signal of 64/100 (Good) with 4 views, 1 installs and 0 GitHub stars. Shipi18n has 44/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.