A side-by-side look at the Shipi18n and Translation AI MCP 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 Translation AI MCP 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 Shipi18n when
You need dedicated capabilities in the Translation Services domain.
No tool names declared yet. Check the project README from the listing page.
Translation AI MCP 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 is categorized under Translation Services and uses a local stdio subprocess. Translation AI MCP belongs to Translation Services and uses a local stdio subprocess. Pick Shipi18n for translation services work and Translation AI MCP 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. Translation AI MCP 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 translation-ai-mcp 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. Translation AI MCP has 41/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.