What's New
Bluente has released an open-source MCP (Model Context Protocol) server that brings professional document translation directly into AI development environments. The server, available on GitHub under MIT license, enables AI agents in Claude Desktop, Cursor, and other MCP-compatible tools to translate documents while preserving original formatting—tables, legal numbering, tracked changes, and layout remain intact.
The integration addresses a specific workflow friction: developers and professionals working across languages previously had to leave their coding environment, upload documents to separate translation tools, wait for output, then manually fix broken formatting. Now, translation happens within the same workflow context.
How It Works
The MCP server exposes six tools that handle the complete translation lifecycle:
{
"tools": [
"language_discovery",
"file_upload",
"translation_initiation",
"status_check",
"result_retrieval",
"batch_processing"
]
}
Technical Implementation:
- Supports 120+ languages and translation pairs
- Handles PDF, DOCX, XLSX, PPTX, and other professional document formats
- Preserves formatting through Bluente's proprietary document processing engine
- Exposes REST-like endpoints through MCP's standardized protocol
Setup Example (Claude Desktop):
// claude_desktop_config.json
{
"mcpServers": {
"bluente-translate": {
"command": "npx",
"args": ["@bluente/mcp-server"],
"env": {
"BLUENTE_API_KEY": "your_key_here"
}
}
}
}
Once configured, the translation tools become available directly in Claude's interface. You can ask Claude to "translate this contract from Spanish to English" while referencing a document in your workspace, and it will handle the entire process through the MCP server.
Practical Takeaways
For Developers Working with International Codebases:
- Documentation Translation: Translate API documentation, README files, and technical specifications without breaking markdown formatting
- Client Communication: Process client documents (requirements, contracts, reports) directly within your development environment
- Code Comments: Translate code comments and variable names when working with multilingual teams
Workflow Integration:
- In Cursor: Use the
/translatecommand or ask the AI assistant to process documents in your project - In Claude Desktop: Reference local files in conversation and let Claude handle the translation through MCP
- Batch processing for multiple documents in a single operation
Limitations to Consider:
- Requires Bluente API key (free tier available, paid for high-volume usage)
- Translation quality varies by language pair and document complexity
- Large documents may have processing delays
- Format preservation works best with standard document formats
Broader Context
This release is part of a growing ecosystem of MCP servers that extend AI coding assistants beyond code generation. Unlike general-purpose translation APIs, Bluente's server specifically targets the document translation needs of professionals—legal contracts, financial reports, technical documentation—where format preservation is critical.
Comparison to Alternatives:
- Google Translate API: Requires custom integration, doesn't preserve document formatting
- DeepL API: Excellent translation quality but limited document format support
- Manual workflow: Previously required switching between multiple tools, losing context
MCP Ecosystem Growth: The Bluente server joins other specialized MCP servers like Figma Console MCP (mentioned in the Medium article) and various tools showcased in the VS Code AI Toolkit's Tool Catalog. This trend indicates that MCP is becoming the standard protocol for extending AI coding assistants with domain-specific capabilities.
For developers already using Claude or Cursor with MCP, adding Bluente's translation server is a straightforward way to eliminate a common workflow interruption. The open-source nature means you can inspect the implementation, contribute improvements, or fork it for custom needs.
