Deepl vs Shipi18n

A side-by-side look at the Deepl and Shipi18n MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Deepl logoDeeplTranslation Services · Local subprocess (stdio)DeepL translation: translate, usage, source/target languages. Free 500k chars/mo.45FairAuth: not declaredShipi18n logoShipi18nTranslation Services · Local subprocess (stdio)Translation QA for locale files: keyless validators, semantic review and BYO-key translation44FairAuth: not declared

Verdict: choose Deepl 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?

Deepl logoChoose Deepl when

  • You need dedicated capabilities in the Translation Services domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: PLATFORM_DEEPL_KEY.
Explore Deepl

Shipi18n logoChoose Shipi18n when

  • You need dedicated capabilities in the Translation Services domain.
  • You prefer a local stdio subprocess transport.
Explore Shipi18n

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDeepl logoDeeplShipi18n logoShipi18n
CategoryTranslation ServicesTranslation Services
Quality signal45/100 · Fair44/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsPLATFORM_DEEPL_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars00
Directory activity 5 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Deepl 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.

Deepl

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "deepl": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-deepl"
      ],
      "env": {
        "PLATFORM_DEEPL_KEY": "YOUR_PLATFORM_DEEPL_KEY_HERE"
      }
    }
  }
}

Shipi18n

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "shipi18n": {
      "command": "npx",
      "args": [
        "-y",
        "@shipi18n/cli"
      ]
    }
  }
}

Frequently asked questions

Deepl is categorized under Translation Services and uses a local stdio subprocess. Shipi18n belongs to Translation Services and uses a local stdio subprocess. Pick Deepl 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.

Deepl has no declared pricing — check the project's own site. 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 deepl and shipi18n as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Deepl has a quality signal of 45/100 (Fair) with 5 views, 0 installs and 0 GitHub stars. Shipi18n has 44/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.