Translation
LILT MCP connector
The LILT connector brings translation jobs, source files, documents and LILT Create content into Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so your team can start, check and update translation work from a chat window while signed in as themselves.
- Connects with an API key
- Free 14-day trial
- No credit card
Claude
Elaichi connected
Which LILT documents finished translation this week?
Working in LILT with Elaichi
-
List all LILT create content
-
-
Governance
/
Audit log
Last 24 hours
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
ChatGPT · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect LILT to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
LILT MCP connector for 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.
LILT MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
LILT MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
LILT MCP connector for 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.
LILT MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with LILT through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in LILT is logged.
-
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.”
What connecting LILT gets you
6 screens from Elaichi, each doing one job for your LILT account.
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, Cursor or Microsoft Copilot
The agent
Ask about LILT documents in plain language.
Answers come from live LILT documents, domains and content, not a stale export.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach LILT.
One org MCP endpoint over OAuth, no SDK and no shared LILT API key.
ElaichiToolsTool catalog
75 LILT tools are ready to call.
Documents, domains, content and file labels are covered with no custom code.
ElaichiToolboxesToolboxes
Each team gets its own LILT toolbox.
Localisation, marketing and support see only the LILT toolbox scoped to them.
ElaichiConnectionsShared connections
Teammates use LILT without seeing credentials.
The connections table shows who connected each LILT account and who it reaches.
ElaichiAudit logAudit log
Every LILT call is written down.
When, who, what happened, type and resource for each LILT document touched.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
LILT digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
LILT
Queued
Automations
A schedule runs LILT work end to end.
Six steps fetch LILT documents, group them, draft a digest, then post it back.
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%
Collections and dashboards
LILT numbers arrive before anyone asks.
Four metrics, 14 days of documents created and a team breakdown, computed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for LILT
All three can connect LILT to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over LILT tools | Allow or restrict single LILT tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per LILT call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting deletes or updates entirely. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot and every other client at the same time.
Does the LILT MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. LILT is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for LILT?
Yes. Both let Claude, ChatGPT or Cursor use LILT. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every LILT call.
How is Elaichi different from Composio for LILT?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to LILT: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put LILT in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
- ChatGPT
- Claude
- Cursor
- Microsoft Copilot