@pipeworx/translate
Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/translate’s. Install: one-click buttons
Connect to just the @pipeworx/translate pack
https://gateway.pipeworx.io/translate/mcp — only @pipeworx/translate’s own tools, nothing else in the catalog.
No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.
Tools: 3
Translate text, detect a language, or list supported languages against any LibreTranslate-compatible instance.
You need to bring an instance or a key. For translation that works with no key of your own, use mymemory — mymemory_translate is keyless. deepl_translate also covers this when its shared platform key has monthly budget left.
Tools
| Tool | What it does |
|---|---|
translate | Translate text between two languages |
detect_language | Detect the language of a string, with confidence |
list_languages | Language codes the configured instance supports |
Auth
Bring your own, one of:
_apiKey— an API key from https://portal.libretranslate.com (libretranslate.com is now key-only)_endpoint— the base URL of a self-hosted instance (https://github.com/LibreTranslate/LibreTranslate)
Given neither, every tool returns {found: false, reason: "requires_key_or_endpoint"} with a pointer to deepl_translate. It does not attempt the call.
Why it is gated
This pack used to hardcode libretranslate.com and call it with no key. That endpoint moved behind an API key, so every call returned the upstream’s raw 400 — “Visit portal.libretranslate.com to get an API key” — which reads to a caller as Pipeworx being broken rather than as a source needing a key.
The obvious fallback was a free public mirror. There aren’t any left. Checked 2026-08-06:
| Instance | Result |
|---|---|
translate.argosopentech.com | does not resolve |
libretranslate.com | 400, key required |
translate.terraprint.co | 502 |
lt.vern.cc | 502 |
translate.fedilab.app | 403 |
libretranslate.eownerdead.dedyn.io | 403 |
trans.zillyhuhn.com | 403 |
So the pack is honestly BYO rather than quietly broken. It is registered in the gateway’s BYO_ONLY_KEY_PACKS, which sinks it below the keyless mymemory_translate in routing and labels it, so an agent asking to translate something reaches the tool that can answer.
Data source
LibreTranslate API v1 — https://github.com/LibreTranslate/LibreTranslate#api
Tools
- translate — Translate text between languages using a LibreTranslate instance you supply — pass _apiKey for libretranslate.com or _endpoint for a self-hosted server. For translation with no key of your own, call m
- detect_language — Detect the language of a text string. Returns an array of detected languages with confidence scores.
- list_languages — List all languages supported by the translation API. Returns language codes and names.
Tools
detect_language— Detect the language of a text string. Returns an array of detected languages with confidence scores.list_languages— List all languages supported by the translation API. Returns language codes and names.translate— Translate text between languages using a LibreTranslate instance you supply — pass _apiKey for libretranslate.com or _endpoint for a self-hosted server. For translation with no key of your own, call m