Lucca MCP connector
The Lucca connector brings employees, employments, departments, legal entities, job positions and probationary periods into Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so each person can look up Lucca HR records inside their own access with every call logged.
- App credentials
- Free 14-day trial
- No credit card
List employees in the Paris business establishment.
Working in Lucca with Elaichi
-
List all Lucca employees
-
Get single Lucca employee by ID
-
List all Lucca legal entities
How to connect Lucca to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Lucca 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.
Lucca 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.
Lucca 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.
Lucca 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.
Lucca 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 Lucca 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 Lucca through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Lucca is logged.
-
HR
Answer a headcount question in seconds
Ask how many people sit in a department or legal entity in Lucca and get the list back without opening a report builder.
-
HR
Check which probationary periods end soon
Pull the probationary periods recorded in Lucca and see whose review date is coming up before the manager asks.
-
People Ops
Look up an employee's employment history
Bring back a person's employments, job position, occupation category and profession from Lucca in one place ahead of a career conversation.
-
Managers
See who is on my team
Ask for the employees in your department in Lucca, with their job positions and establishments, when you are preparing a one-to-one or planning cover.
-
Finance
Reconcile headcount by legal entity
List employees and employments per legal entity and business establishment in Lucca to check them against payroll and budget figures at month end.
-
IT
Verify org structure before a directory sync
Compare departments, establishments and employee records in Lucca against your identity provider to catch mismatches before they cause access problems.
Try asking
- “List employees in the Paris business establishment.”
- “Which departments gained job positions this quarter?”
- “Show employments starting next month by legal entity.”
What connecting Lucca gets you
6 screens from Elaichi, each doing one job for your Lucca account.
Ask Elaichi to work across your apps.
List employees in the Paris business establishment.
Which departments gained job positions this quarter?
Show employments starting next month by legal entity.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about employees, get live Lucca answers.
Plain language questions read employments, departments and job positions from Lucca.
Copy the endpoint
AI apps
One Lucca endpoint for every MCP client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, no SDK, no shared key.
Tool catalog
35 Lucca tools ready without custom code.
Employees, employments, departments, legal entities and job positions, each with list and get methods.
Toolboxes
Every team gets its own Lucca toolbox.
Curate one toolbox per team so People, Payroll and Finance see different Lucca tools.
Shared connections
Share Lucca access, never the credential.
One connected Lucca account serves whole teams while the login stays with its owner.
Audit log
Every Lucca call is on the record.
When, who, what happened, type and resource for each employee and employment read.
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.
Lucca digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch employees
Lucca
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
Lucca
Queued
Automations
A schedule runs the whole Lucca digest.
Fetch employments, group by department, draft a digest, approve it, post back to Lucca.
Lucca health
Refreshed 4 minutes ago · every 15 minutes · from the employees collection
Employees
1,284 ↓ 12%
Employments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Employees created
Last 14 days
By team
Share of activity
People Ops 34%
Payroll France 27%
Recruiting 21%
Finance 18%
Collections and dashboards
Lucca headcount numbers arrive before you ask.
Four metrics, 14 days of new employee records and a department breakdown, computed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Lucca
All three can connect Lucca 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 Lucca tools | Allow or restrict single Lucca 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 Lucca 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.
Lucca tools for your AI agents
35 tools are ready to call through Elaichi's MCP endpoint the moment you connect Lucca, 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 Lucca to Claude?
Two steps. In Elaichi, choose Lucca and enter your Lucca app credentials; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks, and Lucca is ready to use.
Does Lucca work with ChatGPT and Cursor as well as Claude?
Yes. Once Lucca 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 Lucca once and every client you sign in to can use it.
What can an AI agent actually do with my Lucca data?
With Lucca connected, an agent can look up employees, their employments and personal records, and the structure around them: departments, legal entities, business establishments, job positions, professions, occupation categories, job qualifications, probationary periods and employment templates. That means questions like who is in the Paris establishment, whose probationary period ends this month, or which job positions exist in a department get answered from live Lucca records. Because Lucca has many lookups, short concrete asks such as list departments work better than long sentences.
Does connecting Lucca give the AI everything in my HR system?
No. When you connect Lucca through Elaichi the agent works inside your own Lucca access, so it sees only the employees, personal records and entities you are allowed to see. Elaichi can narrow that further with restrictions per role or per person, and it can never widen access beyond what Lucca already grants you.
Can I stop an agent from deleting or changing things in Lucca?
The Lucca connector in Elaichi is read-only today: it looks up employees, employments and organization records and does not create, edit or delete anything in Lucca. On top of that, restrictions in Elaichi work per action, and any action you restrict 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 Lucca connection when someone leaves?
Offboarding a person in Elaichi ends their access to Lucca through every client at once, with no separate steps in Claude, ChatGPT, Cursor or Microsoft Copilot. If they had shared a Lucca connection, it keeps working for everyone else on the team. When you want Lucca gone entirely, disconnecting it once in Elaichi removes it from every client.
Does the Lucca MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Lucca 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 Lucca?
Yes. Both let Claude, ChatGPT or Cursor use Lucca. 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 Lucca call.
How is Elaichi different from Composio for Lucca?
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 Lucca: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Lucca 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