{
  "markdown": "# Translate — LibreTranslate-compatible machine translation\n\nTranslate text, detect a language, or list supported languages against any LibreTranslate-compatible instance.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n**You need to bring an instance or a key.** For translation that works with no key of your own, use [`deepl`](../deepl) — `deepl_translate` covers the same languages and Pipeworx fronts the key.\n\n## Tools\n\n| Tool | What it does |\n|---|---|\n| `translate` | Translate text between two languages |\n| `detect_language` | Detect the language of a string, with confidence |\n| `list_languages` | Language codes the configured instance supports |\n\n## Auth\n\nBring your own, one of:\n\n- `_apiKey` — an API key from <https://portal.libretranslate.com> (libretranslate.com is now key-only)\n- `_endpoint` — the base URL of a self-hosted instance (<https://github.com/LibreTranslate/LibreTranslate>)\n\nGiven neither, every tool returns `{found: false, reason: \"requires_key_or_endpoint\"}` with a pointer to `deepl_translate`. It does not attempt the call.\n\n## Why it is gated\n\nThis 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.\n\nThe obvious fallback was a free public mirror. There aren't any left. Checked 2026-08-06:\n\n| Instance | Result |\n|---|---|\n| `translate.argosopentech.com` | does not resolve |\n| `libretranslate.com` | 400, key required |\n| `translate.terraprint.co` | 502 |\n| `lt.vern.cc` | 502 |\n| `translate.fedilab.app` | 403 |\n| `libretranslate.eownerdead.dedyn.io` | 403 |\n| `trans.zillyhuhn.com` | 403 |\n\nSo the pack is honestly BYO rather than quietly broken. It is registered in the gateway's `BYO_ONLY_KEY_PACKS`, which sinks it below `deepl_translate` in routing and labels it, so an agent asking to translate something reaches the tool that can answer.\n\n## Data source\n\nLibreTranslate API v1 — <https://github.com/LibreTranslate/LibreTranslate#api>\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"translate\": {\n      \"url\": \"https://gateway.pipeworx.io/translate/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/translate/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Translate data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 4226,
  "sha": "843ff243fd43ab916cb9430a8b496f5e1d7a7137dc9991add673df1a1aad9976",
  "repo_slug": "pipeworx-io/mcp-translate",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_translate_89bc7b98/readme"
}