LILT V4 Assist and Bluente's MCP server represent two different translation architectures. LILT Assist is an autonomous agent that lives inside LILT's platform and runs content operations end to end. Bluente's MCP server is a callable translation tool that any agent — Claude, Cursor, an internal LangGraph workflow — invokes when it needs a document translated with formatting preserved. Use Assist when your translation workflow lives entirely inside LILT; use Bluente's MCP server when translation is one capability inside a broader agentic stack.
Bluente is an AI-powered document translation platform used by 30,000+ professionals to translate files in 120+ languages while preserving the original formatting. The architectural distinction matters because the same word — "agentic" — is now applied to fundamentally different shapes, and buyers are making vendor decisions based on assumptions that don't hold.
What Does LILT V4 Assist Actually Do?
LILT V4 launched in April 2026 with a unified PDF pipeline (text-based, scanned, and mixed PDFs handled in one flow), 67 new languages, and the Assist autonomous content operator. Assist is positioned as "agentic global content operations" — a single agent that takes a translation brief, plans the work across LILT's adaptive MT, runs quality checks, surfaces flags for human review, and ships the localized output. It is a closed-loop system inside LILT's platform.
In practice, Assist works best when (a) your content workflow centralizes inside LILT, (b) you have a localization team driving translation strategy, and (c) you want LILT to own the orchestration layer. It is a TMS-plus-agent rather than a callable component.
What Is Bluente's MCP Server?
Bluente publishes an MCP (Model Context Protocol) server — an open-source GitHub repository (Bluente/bluente-translate-mcp-server) — that exposes document translation as a tool any MCP-aware agent can call. Connect it to Claude, Cursor, ChatGPT enterprise via the MCP gateway, or any LangGraph/CrewAI orchestration, and the agent gets a "translate this document" capability that returns a layout-preserved DOCX, PDF, XLSX, or PPTX.
The architectural shape is the opposite of Assist. Translation is one tool in the agent's toolbox, not the agent itself. The agent owns the orchestration; Bluente handles the translation primitive.
Which Architecture Fits Which Job?
Three patterns map cleanly.
Pattern 1 — Localization-first content operations. If your team owns translation as a discrete function (a Localization Manager, a content calendar, a TMS), an agent-inside-the-TMS like LILT Assist is the right shape. The orchestration logic is already inside the localization tool; making it agentic is an upgrade in place.
Pattern 2 — Document translation embedded in a broader AI workflow. If translation is one step inside an autonomous workflow — an M&A diligence agent translating a Spanish contract, a compliance agent translating a Korean call transcript, a legal research agent translating a Japanese case citation — the agent already exists and just needs translation as a tool. Bluente's MCP server fits this cleanly. The agent stays in control, and translation behaves like any other callable capability.
Pattern 3 — Self-serve professional translation. Lawyers, bankers, and consultants translating their own documents on demand — no localization manager, no agent, no orchestration. This is what 30,000+ professionals do on the Bluente web app today. Neither Assist nor an MCP server is involved; the user uploads a file, gets it back in 2 minutes with formatting intact.
The mistake we see most often is buyers comparing Assist to a translation API expecting feature parity. They are different categories.
How Do the Two Architectures Treat Format Preservation?
This is the differentiator that bleeds into the architecture choice. LILT's V4 unified PDF pipeline is genuinely improved on layout — text-based, scanned, and mixed PDFs handled in one flow is a real win. Bluente's engine is built around layout preservation as the primary requirement, which is why it powers in-house counsel, banking, and regulated workflows where the translated file has to be a drop-in replacement for the source. Both handle PDFs well in 2026; the test that matters is whether tables in a 100-page IPO prospectus survive translation untouched. Procurement teams should request a working sample before committing.
For agent workflows specifically, format preservation matters more, not less. If an agent translates a contract and then passes it to a review agent, a signature agent, or a redlining agent downstream, any layout corruption breaks the chain.
Where Does MCP Distribution Matter?
In May 2026 it matters more than it did six months ago. MCP servers are now discoverable through directories: PulseMCP, MCP Atlas, Docker MCP Catalog, mcp.directory. Smartling, Lara, and others have shipped MCP servers that appear in those directories. Bluente's MCP server is in the GitHub repo and is being expanded into directory listings; if your evaluation criterion is "can my Claude agent discover this without custom integration," the directory presence matters operationally.
LILT's MCP and A2A surfaces continue to evolve and are part of its agentic narrative; they do not replace Assist as the primary product but make Assist composable.
What About Speed, Languages, and Cost?
LILT V4 added 67 new languages in April and claims 7.5× faster instant translations on the new release. Bluente supports 120+ languages with translations typically completing in under 2 minutes for most professional documents, and prices at under $0.60 per page versus the $0.10–0.20 per word that traditional agencies and some enterprise platforms charge. Both numbers are real; the right comparison is your specific workflow, not headline metrics.
How Should a Procurement Team Choose?
Three questions cut through the noise:
1. Does translation live inside a TMS-class system that owns your content operations? If yes, an agent-inside-the-TMS (Assist) is the natural shape. If no, translation is better handled as a callable component. 2. Does your stack already include an AI agent (Claude, Cursor, LangGraph) that handles other work? If yes, you want translation as a tool that agent invokes — the MCP server pattern fits, and Bluente's GitHub repo is the easiest path. 3. How much does layout fidelity matter for the documents you translate? Contracts, prospectuses, board minutes, regulatory filings — formatting determines whether the output is usable. Layout-first platforms (Bluente) sit closer to that requirement than text-first or TMS-first platforms.
Frequently Asked Questions
Q: Can Bluente's MCP server be called from inside LILT? In principle, any MCP-aware host can call any MCP server. In practice, LILT's Assist is a closed orchestration today, so direct in-platform integration depends on LILT's roadmap. The more common pattern is: orchestration agent calls both Bluente (for layout-preserved document translation) and LILT (for adaptive-MT string work) as separate tools, depending on the job.
Q: Does LILT Assist preserve format the way Bluente does? LILT V4's unified PDF pipeline materially improved layout handling. For the most complex regulated documents — large financial filings, redlined contracts with tracked changes, scanned exhibits — Bluente is built around layout preservation as the primary requirement. Run a real document through both and compare side by side; that is the only test that matters.
Q: Is Bluente's MCP server free? The MCP server itself is open source on GitHub. Translation usage is metered through the Bluente Translation API (under $0.60/page, with free trial credits). There is no per-seat or per-agent licensing on the MCP layer.
Q: Which architecture is "more agentic"? The word "agentic" is overloaded. Assist is an autonomous agent built by LILT for content operations. Bluente's MCP server is a callable tool that lets any agent — including ones you build yourself — do format-preserving document translation. Neither is more agentic; they are different shapes for different jobs.
Q: What if our team needs both? Common in 2026. A localization team uses Assist for the content-ops pipeline; an in-house counsel team uses Bluente's MCP server inside a Claude legal agent for contract translation. They are not mutually exclusive, and the procurement decisions are made by different owners.
Q: How secure is Bluente's MCP server for confidential documents? The MCP server inherits Bluente's platform security: SOC 2 Type II, ISO 27001:2022, GDPR, zero data retention with 24-hour auto-delete, and a commitment that customer documents are never used to train models. For BYOK or EU-only processing, the enterprise tier covers both.
Start translating documents for free. Bluente preserves your formatting across 120+ languages in under 2 minutes. Try BluTranslate free — no credit card required.