bluente-translate

by bluente

Not rated
GitHub

About

Translate your documents with formatting intact in 2 minutes

Details

Author
bluente
Categories
Productivity, Other

Setup

Install bluente-translate in your MCP client (Claude Desktop, Cursor, Windsurf, and others).

Repository: https://github.com/bluente/bluente-translate-mcp-server

Follow the installation instructions in the repository README, then restart your MCP client.

Translate your documents with formatting intact in 2 minutes

AI-powered. Format-preserving. Built for professional document translation workflows.

bluente-translate-mcp-serveris the official open-source MCP server for exposing Bluente translation capabilities to AI clients.

It wraps Bluente APIs into production-ready MCP tools so teams can automate multilingual document workflows from Claude Desktop, Cursor, and other MCP-compatible runtimes.

Bluente focuses on enterprise-grade document translation whereaccuracy, formatting integrity, and speedmatter.

FromBluente.comandBlu Translate, the core product positioning is:

- AI-powered translation for professional use cases
- Original layout retention for document-centric workflows
- Broad language and file-type support
- Security-first handling for sensitive content

This MCP server brings those capabilities into agent workflows through a standard protocol interface.

This repository is maintained byBluenteand is part of Bluente's public developer ecosystem.

- Company website:https://www.bluente.com
- Product page:
https://www.bluente.com/translator
- API docs:
https://www.bluente.com/docs

- What You Get
-
Architecture
-
Supported Bluente APIs
-
MCP Tools
-
Quick Start
-
Local Development
-
Operational Notes
-
Data Handling & Privacy
-
Security
-
Roadmap
-
Contributing and Governance
-
License

- Modular Node.js MCP server with clear layering (config,client,service,tools)
- One-file-per-tool implementation for maintainability
- Unified tool response envelope (ok/tool/dataand structured errors)
- End-to-end translation workflow tool (upload -> start -> poll -> download)
- CI checks and local smoke tests

AI Client (Claude / Cursor / Agents) | | MCP (stdio) v +---------------------------------------+ | Bluente Translate MCP Server | | | | tools/ -> MCP tool handlers | | services/ -> workflow orchestration | | clients/ -> Bluente HTTP API client | | config/ + lib/ -> env/errors/results | +---------------------------------------+ | | HTTPS v Bluente Translation APIs
src/ clients/bluente-http-client.js config/env.js constants/api.js lib/errors.js lib/mcp-result.js services/translation-workflow-service.js tools/.tool.js tools/schemas.js tools/register-tools.js server.js index.js tests/smoke/core-smoke.test.js

- GET /blu_translate/supported_languages
- POST /blu_translate/upload
- GET /blu_translate/check
- POST /blu_translate/translate
- GET /blu_translate/download

- bluente_get_supported_languages
- bluente_upload_file
- bluente_get_translation_status
- bluente_translate_file
- bluente_download_file
- bluente_translate_document_workflow

- bluente_translate_file:fromandtoare required whenaction="start"and optional whenaction="cancel".
- bluente_translate_document_workflow:status_entryis configurable (pdforword) for status polling.

{ "ok": true, "tool": "bluente_upload_file", "data": { "code": 0, "message": "success", "data": { "id": "task_xxx" } } }
{ "isError": true, "ok": false, "tool": "bluente_translate_file", "error": { "name": "BluenteApiError", "message": "Bluente API request failed.", "details": { "status": 401 } } }

Requirements: Node.js>= 20(check withnode --version; install fromnodejs.org) and a Bluente API key.

Getting an API key:log in attranslate.bluente.comand go toMy Files → API Keys and Webhook. Treat the key like a password — it authorizes translations billed to your account, so keep it out of version control and shared documents.

Option 1: Just let your coding agent do it

The fastest way to install: don't. If you use Claude Code, Cursor, or any MCP-capable coding agent, paste this prompt and watch it handle everything — config file, key, verification — in under a minute. ReplaceYOUR_KEY_HEREwith your API key:

Install the Bluente Translate MCP server into this client. It's the npm package@bluente/translate-mcp-server, run vianpx -y @bluente/translate-mcp-server(stdio), and it needs the environment variableBLUENTE_API_KEYset in the server config'senvblock. UseYOUR_KEY_HEREas the key. After configuring, verify the installation by calling thebluente_get_supported_languagestool and show me the result. Docs:https://github.com/Bluente/bluente-translate-mcp-server

The agent finds the right config file for its client, writes the block, and proves the install works by showing you the supported-language list.

Prefer not to paste your API key into an agent conversation? Have the agent useREPLACE_MEas the key, then edit the config file by hand and restart your client.
-

OpenSettings → Developer → Edit Config(opensclaude_desktop_config.json).

Add this block (merge intomcpServersif it already exists), inserting your API key:

{ "mcpServers": { "bluente-translate": { "command": "npx", "args": ["-y", "@bluente/translate-mcp-server"], "env": { "BLUENTE_API_KEY": "your_api_key_here" } } } }

Quit and reopen Claude Desktop. The tools icon should list sixbluente_tools.

Claude Code— one command, then restart your session and verify with/mcp:

claude mcp add bluente-translate -e BLUENTE_API_KEY=your_api_key_here -- npx -y @bluente/translate-mcp-server

Cursor— Settings → MCP → Add server, or create.cursor/mcp.jsonin your project with the same JSON block as Claude Desktop.

Smoke test (any client):ask"What languages does Bluente translation support?"— a free, read-only call. A language list back means the key and connection both work. The first run takes a few extra seconds whilenpxdownloads the package.

The server readsBLUENTE_API_KEYfrom its environment — you never pass it as a tool argument or store it in a file. If the server reportsMissing BLUENTE_API_KEY, the key is not reaching the server process: check theenvblock for typos and restart your client. When testing from a terminal, prefix the server command itself (BLUENTE_API_KEY=your_api_key_here npx -y @bluente/translate-mcp-server); in a shell pipeline the assignment must sit directly beforenpx— placed at the start of the line it applies only to the first command in the pipe.

git clone https://github.com/bluente/bluente-translate-mcp-server.git cd bluente-translate-mcp-server npm install cp .env.example .env # then set BLUENTE_API_KEY npm start # run the server on stdio npm run check # syntax check npm test # run tests

To point an MCP client at your local checkout, use"command": "node"with"args": ["/absolute/path/to/bluente-translate-mcp-server/src/index.js"]instead of thenpxconfig above.

- Workflow tool polls until terminal state (READYorERROR).
- Output download can be disabled withauto_download=false.
- Timeout is configurable viaBLUENTE_API_TIMEOUT_MS.
- For production, use separate API keys per environment.

- Documents you translate are uploaded to Bluente's API(api.bluente.comby default) for processing. Do not translate documents you are not permitted to send to a third-party service.
- The AI model controls the tools.When run locally (stdio),file_pathlets the model read any file your user account can read and upload it to Bluente, andoutput_pathlets it write downloaded files to any writable path. Review tool calls in your MCP client before approving them, especially when working with untrusted documents — a malicious document could try to instruct the model to misuse these tools.
- Translated output returned by tools (file contents, status payloads) enters your AI client's context and is therefore visible to your LLM provider.
- Your API key stays on your machine: it is read from the environment and sent only as anAuthorizationheader to the configured Bluente API base URL. It is never logged or included in tool responses.

- Do not commit API keys or.envfiles.
- Rotate leaked keys immediately.
- Use repository private vulnerability reporting.

- Add text translation tools if exposed in public API docs
- Add richer integration tests with API mocking
- Add container image and one-command local launch profile

- Contribution guide:CONTRIBUTING.md
- Security policy:
SECURITY.md
- Changelog:
CHANGELOG.md
- Code ownership:
.github/CODEOWNERS

Bluente builds AI translation and business communication solutions for professional teams.

- Website:bluente.com
- Product page:
Blu Translate
- API documentation:
bluente.com/docs

Evaluates technical documentation against globalization standards, analyzing for translation issues, ambiguity, and sentence length.

An example MCP server for translating documents, designed for deployment on Cloudflare Workers.

Quran-focused MCP server for ayah translation, tafsir, mutashabihat lookups, recitation playlists, and prayer times.

Study the Bible in its original languages, trace themes across both testaments, and compare five translations — all in one conversation. Ask any question about what Scripture says and get grounded, cited answers: What does the Bible say about suffering? Topical search surfaces Job as the Bible's principal witness on suffering (with explanations of why it matters and suggested starting passages), Psalms on lament, Romans on justification — whole books and narratives alongside individual verses. What is the Hebrew word behind lovingkindness in Psalm 23? Compare how KJV and WEB translate John 3:16. Trace the word grace through Paul's letters. Covers 155,510 verses across KJV, WEB, ASV, YLT, and Darby with 606,140 cross-references, 17,543 Strong's entries, BDB and Thayer lexicon definitions, and Nave's 5,319 topical categories.

Ukrainian language authenticity checker against English and russian calques

Automated document processing and extraction

Contract and template management for drafting, reviewing, and sending binding contracts.

Convert files (DOCX, XLSX, PPTX, images), HTML, and Markdown to pixel-perfect PDFs — npx stdio or hosted Streamable HTTP, free API key in one click.

Kamai is an AI takeoff platform that reads your construction blueprints and instantly extracts the quantities, measurements, and materials you need to estimate and bid jobs faster.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.