bluente_get_supported_languagesLABSCO SUMMARY
One call for the happy path, four for when you need the pieces.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command plus a key — npx -y @bluente/translate-mcp-server, then supply credentials
USE CASES
01
Translating a contract with its formatting intact
Hand over the file and the target language; the upload, start, poll and download run as one call.
02
Checking a language pair is supported first
List what the API accepts before uploading anything.
03
Watching a long job and fetching the result
Poll the task yourself, then download when it reports finished.
04
Cancelling a job started by mistake
The same tool that starts a translation also cancels one, without needing the language pair again.
6 tools
Listed in project docs. Your client may show a different list.
bluente_upload_filebluente_get_translation_statusbluente_translate_filebluente_download_filebluente_translate_document_workflowBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
- npx on PATH
- BLUENTE_API_KEY in your environment
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @bluente/translate-mcp-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"bluente-translate": {
"command": "npx",
"args": [
"-y",
"@bluente/translate-mcp-server"
],
"env": {
"BLUENTE_API_KEY": "<YOUR_BLUENTE_API_KEY>"
}
}
}
}Settings → Developer → Edit Config (opens claude_desktop_config.json), then quit and reopen
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add bluente-translate -e BLUENTE_API_KEY=<YOUR_BLUENTE_API_KEY> -- npx -y @bluente/translate-mcp-serverCursor
CURSOR · JSON
{
"mcpServers": {
"bluente-translate": {
"command": "npx",
"args": [
"-y",
"@bluente/translate-mcp-server"
],
"env": {
"BLUENTE_API_KEY": "<YOUR_BLUENTE_API_KEY>"
}
}
}
}Settings → MCP → Add server, or create .cursor/mcp.json with the same JSON block as Claude Desktop
