HRIS
Kallidus MCP connector
The Kallidus connector brings courses, lessons, compliance statuses, job profiles, user groups and learners into Claude, ChatGPT, Cursor and the Elaichi Agent, so people can ask about training and compliance in plain language within their own Kallidus access.
-
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 Kallidus to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Kallidus once
-
Open Connections, choose Add connection, and pick Kallidus.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste your Kallidus app credentials. Kallidus 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 Kallidus 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 Kallidus 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 Kallidus 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 Kallidus 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 Kallidus through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Learning and development
Find who has not finished mandatory training
Ask which learners still have a course or lesson outstanding and get the list back from Kallidus course and lesson statuses, ready to chase before the deadline.
-
Compliance
Check compliance status before an audit
Pull Kallidus compliance summaries and the commentary behind each status so you walk into the audit knowing exactly where the gaps are.
-
HR
Confirm a new starter's onboarding progress
Look up a new employee in Kallidus, see which courses and lessons are assigned and which are complete, and catch up with their manager in one message.
-
People managers
See how your team is tracking
Ask for the course and compliance status of everyone in your Kallidus user group without opening a report or asking L&D to run one.
-
HR
Match job profiles to required learning
Check which Kallidus job profiles are linked to which people, and spot anyone whose role has changed but whose training has not caught up.
-
Operations
Summarize compliance for the leadership meeting
Have the agent read Kallidus compliance details, statuses and commentaries and turn them into a short written summary by team for the monthly review.
Try asking
- “Which employees have overdue compliance training this quarter?”
- “List courses completed by the sales job profile this month.”
- “Show lesson status for new hires in customer support.”
AI tools
Kallidus tools for your AI agents
14 tools are ready to call through Elaichi's MCP endpoint the moment you connect Kallidus, 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 Kallidus gets you
6 screens from the product, each doing one job for your Kallidus account.
The agent
Ask Kallidus questions, get answers instantly.
Ask about courses, compliance status or job profiles in plain language and get live answers.
- courses
- lessons
- compliance statuses
- job profiles
Ask Elaichi to work across your apps.
Which employees have overdue compliance training this quarter?
List courses completed by the sales job profile this month.
Show lesson status for new hires in customer support.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint, every client, no shared keys.
Claude, ChatGPT and Cursor all reach Kallidus through one governed org endpoint over OAuth.
Copy the endpoint
Tool catalog
14 Kallidus tools, zero custom code.
Every Kallidus tool, resource and method is cataloged and ready to use without writing code.
- List all Kallidus compliance details
- List all Kallidus compliance status commentaries
- List all Kallidus compliance statuses
- List all Kallidus compliance summaries
Toolboxes
Every team gets its own Kallidus toolbox.
Learning, compliance and HR teams each work from a toolbox scoped to their own needs.
- HR
- Learning & Development
- Compliance
- People Ops
Shared connections
Teammates use Kallidus, never see the login.
The connections table shows who owns each account and how many teams share it.
- HR EMEA
- Compliance
- L&D
- People Ops
Audit log
Every Kallidus call, logged and attributable.
The audit log records who did what, when, and which resource it 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 triggers real Kallidus work, approved.
A trigger fetches courses, drafts a digest, and waits for approval before posting back.
Kallidus digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch courses
Kallidus
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
Kallidus
Queued
Collections and dashboards
Kallidus numbers, refreshed without a model.
A live dashboard tracks course completion and compliance status by team, no prompting required.
Kallidus health
Refreshed 4 minutes ago · every 15 minutes · from the courses collection
Courses
1,284 ↓ 12%
Lessons
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Courses created
Last 14 days
By team
Share of activity
HR EMEA 34%
Compliance 27%
L&D 21%
People Ops 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Kallidus to Claude?
First connect Kallidus in Elaichi by entering your Kallidus app credentials, which takes a minute and needs 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. Claude asks you to sign in to Elaichi, and from then on Kallidus courses, lessons, learners and compliance statuses are available in the conversation.
Does Kallidus work with ChatGPT and Cursor as well as Claude?
Yes. Once Kallidus 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 Kallidus once and every client picks it up.
What can an AI agent actually do with my Kallidus data?
An agent connected to Kallidus can look up learners, user groups and job profiles, list courses and lessons, and read course, lesson and compliance statuses along with the commentary attached to them. In practice that means asking who has not completed a mandatory course, how a team is tracking on compliance, or what training a new starter still has left. This connector reads from Kallidus; it does not create or change records.
Does connecting Kallidus give the AI access to every learner and every record?
No. Every request to Kallidus runs inside the access of the person who signed in, so someone sees the learners, groups and compliance records their own Kallidus account allows and nothing beyond that. Elaichi can narrow that access further with restrictions, but it can never widen what Kallidus itself permits.
Can I stop an agent from deleting or changing things in Kallidus?
The Kallidus connector only reads records, so an agent cannot delete or change courses, lessons, learners or compliance statuses through it. On top of that, Elaichi restrictions work per action, and any action you block is never shown to Claude, ChatGPT or any other client, so no prompt can reach it.
What happens to a Kallidus connection when someone leaves the company?
When you offboard someone in Elaichi, their access to Kallidus through every connected client ends at once. If they had shared a Kallidus connection with a team, that connection keeps working for everyone else. If you want to remove Kallidus entirely, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor and every other client at the same time.
Put Kallidus in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.