Bluente Translate

What is Bluente Translate?

Bluente Translate is an open-source MCP (Model Context Protocol) server that wraps Bluente’s translation APIs into MCP tools for AI clients. It enables agent-driven multilingual document workflows from MCP-compatible runtimes like Claude Desktop and Cursor, with a focus on accuracy, formatting integrity, and enterprise security.

How to use Bluente Translate?

Install with npm install, copy .env.example to .env, set your BLUENTE_API_KEY and BLUENTE_API_BASE_URL, then run npm start. For client integration (e.g., Claude Desktop), add a JSON entry to your MCP configuration with the path to src/index.js and the same environment variables. Tools are invoked through the MCP protocol.

Key features of Bluente Translate

• Six MCP tools for full translation workflows (upload, translate, status, download, list languages, end-to-end workflow)
• Format-preserving translation for document-centric use cases
• Unified JSON response envelope (ok, tool, data or error)
• Configurable polling, timeout, and output download behavior
• Modular Node.js architecture with clear service, client, and tool layers

Use cases of Bluente Translate

• Automating document translation from an AI assistant (e.g., Claude Desktop)
• Translating files while retaining original layout and formatting
• Integrating enterprise-grade translation into agent workflows

FAQ from Bluente Translate

What are the runtime requirements?

Node.js version 20 or higher and a valid Bluente API key are required.

How do I configure the server?

Set the environment variables BLUENTE_API_KEY, BLUENTE_API_BASE_URL (default https://api.bluente.com/api/20250924), and optionally BLUENTE_API_TIMEOUT_MS (default 90000 ms) in your .env file or client configuration.

What MCP tools does the server provide?

It exposes six tools: bluente_get_supported_languages, bluente_upload_file, bluente_translate_file, bluente_get_translation_status, bluente_download_file, and bluente_translate_document_workflow.

Where do translations get processed?

All translation processing happens on Bluente’s servers via HTTPS API calls. The MCP server acts as a local proxy to those APIs.

What is the security policy for API keys?

API keys must never be committed to version control or .env files. Leaked keys should be rotated immediately. The repository provides a security disclosure process via SECURITY.md.