Document & File Management · LILT MCP + Claude
LILT MCP with Claude: Faster Translation and Localisation Workflows
The short answer
Claude connects to LILT through the Model Context Protocol, an open standard that gives Claude secure, permission-controlled access to LILT's hosted localisation server. Once connected, Claude can create translation jobs, fetch translated content, review untranslated segments and manage glossaries from plain-language instructions, with your team approving important changes.
What is LILT MCP?
LILT MCP is a hosted localisation server that exposes translation workflows and APIs. It lets software tools request translations, track jobs and retrieve finished content. Localisation managers, product teams, content operations staff and developers use it to get websites, apps, help articles and marketing material into multiple languages without rebuilding their processes each time.
How Claude connects to LILT MCP through MCP
The Model Context Protocol, or MCP, is an open standard that lets Claude use other software safely. Think of it as a universal adapter between Claude and a tool. Through it, Claude can read information from LILT and take actions there, using only the permissions your organisation grants.
Once connected, Claude can typically create translation jobs, fetch translated content, check which segments are still untranslated and help maintain glossaries. A product manager could ask Claude in plain English to send new help articles for translation into French and German, then report back what is still pending.
Permissions and approvals keep people in charge. Access is limited to the actions you choose, sign-in uses LILT's supported OAuth method, and consequential steps such as publishing translations or changing approved glossary terms can require a named person's sign-off. Every action is recorded in audit logs.
What you can automate
Translation job requests
Content teams often send batches of pages, emails or product text for translation through several steps. With Claude connected to LILT, a team member can describe the content and target languages in one message. Claude creates the job, attaches the right settings and confirms the reference number, saving time on repetitive set-up.
Retrieving finished translations
Developers and website managers need approved translations back in their systems. Claude can fetch completed content from LILT on request or on a schedule, so the latest approved wording reaches the right place without manual downloads and copying.
Chasing untranslated segments
Before a launch, a localisation lead needs to know what is still missing. Claude can review LILT for untranslated segments, group them by project or language, and produce a short list of what needs attention, so reviewers focus on the gaps that matter.
Glossary management
Brand names, product terms and legal phrases must stay consistent across languages. Claude can help a terminology owner look up, add or update glossary entries through plain-language instructions, while changes to approved terms are routed for review before they take effect.
Status reporting for stakeholders
Operations leaders often ask how many projects are in progress and when they will finish. Claude can summarise translation activity from LILT into a weekly update for management, drawing out delays and upcoming deadlines in simple language.
An end-to-end workflow: Product launch localisation
TriggerA product manager marks a new feature as ready for release in the company's project tracker.
Claude reads the approved feature text from the document system and checks it against the brand glossary in LILT.
Claude creates a translation job in LILT for the agreed languages and sends the source content.
Claude monitors the job and flags any untranslated segments to the localisation lead.
Once translations are complete, the localisation lead approves them and Claude retrieves the final content.
Claude posts the approved translations back to the document system and notifies the launch team in their chat channel.
OutcomeLocalised launch materials arrive on time in every target language, with consistent terminology and a clear audit trail of who approved what.
How we set it up
Free automation audit
We review your current translation and localisation processes, identify the requests and reports that take the most time, and agree which workflows are worth automating first. There is no charge for this step.
Secure connection
We connect Claude to LILT using the DCR OAuth sign-in method that LILT supports, so your team signs in with its own credentials. Access is limited to the least permissions needed for each workflow.
Workflow design
We design the end-to-end process across LILT and your other systems, such as Microsoft 365, your content management system or ticketing tool. We agree which steps need human approval before anything is published.
Testing and launch
We test the workflow against real past projects and check that outputs match what your linguists expect. We then launch with monitoring and audit logs turned on.
Team training
We train your localisation, content and operations staff on how to make requests in plain language, review Claude's work and handle exceptions, so the team can run the workflow confidently.
Who benefits
- Localisation managers
- Fewer manual job set-ups and a clear view of what is still untranslated before each launch.
- Product managers
- Faster route from finished features to localised release materials in every market.
- Content operations teams
- Less copying of text between systems and fewer delays in publishing translated content.
- Operations and IT leaders
- Consistent processes, controlled access and audit logs that show who approved each change.
Security and control
- Least-privilege access: Claude can only use the LILT actions your organisation approves.
- Secure OAuth sign-in with your team's own credentials, with no shared passwords.
- Human approval for consequential steps such as publishing translations or changing approved glossary terms.
- Full audit logs of Claude's actions, so every change can be traced to a request and an approver.
- Regular review of permissions and workflows as your localisation needs change.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can run this workflow with data handling aligned to their own privacy and contractual requirements. In India, the Digital Personal Data Protection Act, 2023 shapes how personal data in translation content is handled. In the UAE and Saudi Arabia, local data protection laws apply, and we help you choose a hosting region for Claude that meets those requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the LILT MCP server do?
The LILT MCP server is a hosted localisation server that exposes translation workflows and APIs through the Model Context Protocol. It allows Claude and other AI tools to create translation jobs, fetch translated content, review untranslated segments and manage glossaries. It gives software a structured, controlled way to work with LILT rather than relying on manual steps.
Is connecting Claude to LILT secure?
Yes, when it is set up correctly. Sign-in uses the DCR OAuth method that LILT supports, so access is tied to your team's credentials rather than shared passwords. We apply least-privilege permissions, require human approval for consequential actions and keep audit logs. Security depends on your configuration, so we review it with you before launch.
What can Claude do with LILT once connected?
Typically, Claude can create translation jobs, fetch translated content, check for untranslated segments and help maintain glossaries, all through natural language requests. It can also summarise activity into status reports. The exact actions are limited to the permissions you approve during setup.
How long does setup take?
Timing depends on how many workflows you want and how many systems they touch. A focused single workflow is often set up within a few weeks, including testing and training. We confirm a realistic timeline during the free automation audit, once we understand your processes.
What LILT plan or permissions do I need?
You need an active LILT account with access to the workspaces and projects you want Claude to use, and permission to authorise OAuth sign-in. The specific plan requirements depend on your LILT agreement, so we recommend checking with your LILT account contact and confirming the details during our audit.