HRIS
Lucca MCP connector
The Lucca connector brings employees, employments, departments, legal entities, job positions and probationary periods into Claude, ChatGPT, Cursor and any MCP client, so each person can look up Lucca HR records inside their own access with every call logged.
-
How it connects. App credentials. 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 Lucca to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Lucca once
-
Open Connections, choose Add connection, and pick Lucca.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste your Lucca app credentials. Lucca authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.
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 Lucca 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 Lucca 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 Lucca 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 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.
Use cases
What teams do with Lucca through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
See it in Elaichi
What connecting Lucca gets you
6 screens from the product, each doing one job for your Lucca account.
The agent
Ask about employees, get live Lucca answers.
Plain language questions read employments, departments and job positions from Lucca.
- employees
- employments
- departments
- job positions
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 or Cursor
MCP clients
One Lucca endpoint for every MCP client.
Claude, ChatGPT and Cursor connect over OAuth, no SDK, no shared key.
Copy the endpoint
Tool catalog
35 Lucca tools ready without custom code.
Employees, employments, departments, legal entities and job positions, each with list and get methods.
- List all Lucca employees
- Get single Lucca employee by ID
- List all Lucca legal entities
- Get single Lucca legal entity by ID
Toolboxes
Every team gets its own Lucca toolbox.
Curate one toolbox per team so People, Payroll and Finance see different Lucca tools.
- People Ops
- Payroll
- Recruiting
- Finance
Shared connections
Share Lucca access, never the credential.
One connected Lucca account serves whole teams while the login stays with its owner.
- People Ops
- Payroll France
- Recruiting
- Finance
Audit log
Every Lucca call is on the record.
When, who, what happened, type and resource for each employee and employment read.
- 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 the whole Lucca digest.
Fetch employments, group by department, draft a digest, approve it, post back to Lucca.
Lucca digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Lucca
Queued
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.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 team 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 block is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.
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 or Cursor. 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.
Put Lucca in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.