Translation
LILT MCP connector
The LILT connector brings translation jobs, source files, documents and LILT Create content into Claude, ChatGPT, Cursor and any MCP client, so your team can start, check and update translation work from a chat window while signed in as themselves.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect LILT to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect LILT once
-
Open Connections, choose Add connection, and pick LILT.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a LILT API key. One person generates a token in LILT and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect LILT to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect LILT to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect LILT to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect LILT to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with LILT through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Localization
Kick off a translation job from chat
Upload the source file, create the job and ask for a status check later, all in plain language. The job and file end up in LILT exactly as if you had done it there.
-
Marketing
Draft campaign copy in several languages
Ask for new LILT Create content for a landing page or email, then read back and revise the draft before it goes to the localization team.
-
Product
Check where release notes stand
List the open translation jobs for a launch and get a quick summary of which files are still waiting, without opening LILT and clicking through each one.
-
Support
Get a help article translated fast
Send an updated help center article to LILT as a document and create a job for the languages your customers speak, then follow up on it by name.
-
Legal
Keep terms and conditions current
Create terms and conditions content in LILT and pull up the version you need when a contract or policy changes, so translated legal text is not left behind.
-
Operations
Tidy files and labels between projects
Label incoming source files, list what has piled up, and remove files that were uploaded by mistake so the LILT workspace stays easy to work in.
Try asking
- “Which LILT documents finished translation this week?”
- “List LILT domains with content awaiting review.”
- “Summarize LILT content created for the German domain.”
AI tools
LILT tools for your AI agents
75 tools are ready to call through Elaichi's MCP endpoint the moment you connect LILT, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting LILT gets you
6 screens from the product, each doing one job for your LILT account.
The agent
Ask about LILT documents in plain language.
Answers come from live LILT documents, domains and content, not a stale export.
- documents
- domains
- content items
- file labels
Ask Elaichi to work across your apps.
Which LILT documents finished translation this week?
List LILT domains with content awaiting review.
Summarize LILT content created for the German domain.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach LILT.
One org MCP endpoint over OAuth, no SDK and no shared LILT API key.
Copy the endpoint
Tool catalog
75 LILT tools are ready to call.
Documents, domains, content and file labels are covered with no custom code.
- Delete a LILT create content by ID
- List all LILT create content
- Get single LILT create content by ID
- Update a LILT create content by ID
Toolboxes
Each team gets its own LILT toolbox.
Localisation, marketing and support see only the LILT toolbox scoped to them.
- Localisation
- Marketing
- Product
- Support
Shared connections
Teammates use LILT without seeing credentials.
The connections table shows who connected each LILT account and who it reaches.
- Localisation EMEA
- Marketing
- Product content
- Support docs
Audit log
Every LILT call is written down.
When, who, what happened, type and resource for each LILT document touched.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule runs LILT work end to end.
Six steps fetch LILT documents, group them, draft a digest, then post it back.
LILT digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch documents
LILT
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
LILT
Queued
Collections and dashboards
LILT numbers arrive before anyone asks.
Four metrics, 14 days of documents created and a team breakdown, computed on schedule.
LILT health
Refreshed 4 minutes ago · every 15 minutes · from the documents collection
Documents
1,284 ↓ 12%
Domains
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Documents created
Last 14 days
By team
Share of activity
Localisation EMEA 34%
Marketing 27%
Product content 21%
Support docs 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect LILT to Claude?
Connect LILT in Elaichi first: paste in your LILT API key and the connector is ready, with no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and from then on it can work with your LILT jobs, files and content.
Does LILT work with ChatGPT and Cursor as well as Claude?
Yes. Once LILT is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect LILT once and every client sees it.
What can an AI agent actually do with my LILT data?
An agent can create and update translation jobs in LILT, upload and label source files, add documents, list the domains you translate for, and draft, read and revise LILT Create content, including terms and conditions and content preferences. It can also list what is in progress and give you a plain summary of where each job stands. Because LILT exposes a lot of actions, short concrete asks such as "list open jobs" or "upload this file" tend to work better than long paragraphs.
Does connecting LILT give the AI access to everything in my LILT account?
No. Every request to LILT runs inside the access of the person who signed in to Elaichi, so the agent sees the same jobs, files and content that person could see in LILT, and nothing more. Elaichi can narrow that further with restrictions, but it can never widen access beyond what LILT itself allows that person.
Can I stop an agent from deleting or changing things in LILT?
Yes. Restrictions in Elaichi work per action, so you can allow an agent to create and read LILT jobs and files while blocking deletes or updates entirely. A blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it.
What happens to a LILT connection when someone leaves?
When you offboard a person in Elaichi, their access to LILT through every AI client ends at once. If they had shared a LILT connection with a team, that connection keeps working for everyone else. If you want LILT gone completely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Put LILT in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.