Document translation is always the same four HTTP steps, and the workflow tool means an assistant does not have to orchestrate them itself or invent a polling loop. The individual tools stay available for the cases where you want to inspect the job between stages, or cancel it.
The official MCP server for Bluente's document translation API. It wraps the upload, start, poll and download sequence both as individual tools and as one call that runs the whole thing end to end.
- bluente_translate_document_workflow runs upload, start, poll and download in a single call; status_entry selects pdf or word for the polling stage
- bluente_upload_file, bluente_translate_file, bluente_get_translation_status and bluente_download_file are the same steps individually
- bluente_get_supported_languages lists the pairs before you commit a file
- bluente_translate_file requires from and to when action is start, and treats them as optional when action is cancel
- Every response arrives in one envelope — ok, tool and data on success; a structured error with the upstream status on failure
Node.js 20 or newer, run as npx -y @bluente/translate-mcp-server over stdio with BLUENTE_API_KEY in the config's env block. The key comes from translate.bluente.com under My Files → API Keys and Webhook, and it authorises translations billed to your account, so keep it out of committed config.
One command plus a key — npx -y @bluente/translate-mcp-server, then supply credentials