HRIS
ShiftCare MCP connector
The ShiftCare connector brings shifts, client notes, staff leave, complaints, teams and facilities into Claude, ChatGPT, Cursor and the Elaichi Agent, so care coordinators can ask questions and update rosters as themselves, with every action recorded.
-
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 ShiftCare to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect ShiftCare once
-
Open Connections, choose Add connection, and pick ShiftCare.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a ShiftCare API key. One person generates a token in ShiftCare 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 ShiftCare 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 ShiftCare 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 ShiftCare 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 ShiftCare 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 ShiftCare through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Rostering
Fill an open shift before the day starts
Ask which shifts are still unfilled for tomorrow at a given facility, then create or update the shift once a support worker confirms they can take it.
-
Care coordination
Write up the visit as soon as it ends
Dictate what happened during a client visit and have it saved as a ShiftCare client note, then correct or add to the note later if something was missed.
-
Quality and compliance
Log a complaint and keep it moving
Record a complaint from a client or family member the moment it arrives, check its current status by asking, and update a batch of complaints when the review meeting closes them out.
-
HR
Record leave and see who is away
Add a support worker's leave request, list everyone on leave for the coming fortnight, and adjust the dates if plans change, without opening the leave calendar.
-
Operations
See how each area and facility is staffed
Pull the list of ShiftCare areas, facilities and teams alongside this week's shifts to spot a site that is running thin before it becomes a problem.
-
Finance and admin
Keep payroll and client IDs lined up
Attach the reference numbers your payroll or funding system uses to the matching ShiftCare records in bulk, so exports and reconciliations match up without hand editing.
Try asking
- “List all open ShiftCare complaints raised this week.”
- “Show approved ShiftCare leaves across every area next month.”
- “Add a client note about today's shift handover.”
AI tools
ShiftCare tools for your AI agents
97 tools are ready to call through Elaichi's MCP endpoint the moment you connect ShiftCare, 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 ShiftCare gets you
6 screens from the product, each doing one job for your ShiftCare account.
The agent
Ask about shifts, get answers from ShiftCare.
Type a question in plain language and read live client notes, leaves and complaints.
- client notes
- complaints
- leaves
- areas
Ask Elaichi to work across your apps.
List all open ShiftCare complaints raised this week.
Show approved ShiftCare leaves across every area next month.
Add a client note about today's shift handover.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach ShiftCare here.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
97 ShiftCare tools ready without custom code.
Browse tool names, resources and methods across clients, leaves, complaints and areas.
- List all ShiftCare account locations
- List all ShiftCare areas
- Create a ShiftCare client note
- Update a ShiftCare client note by ID
Toolboxes
Every team gets its own ShiftCare toolbox.
Rostering, HR and quality each see a curated set of ShiftCare tools.
- Rostering
- People and HR
- Quality and Compliance
- Care Coordination
Shared connections
Share a ShiftCare account, never the credential.
See who connected each account and how many teams and members use it.
- Rostering
- People and HR
- Quality
- Care Coordination North
Audit log
Every ShiftCare call is written down.
When, who, what happened, type and resource, in an append only log.
- 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 fires, ShiftCare work gets done.
Six steps fetch leaves, group them, draft a digest, await approval, then post back.
ShiftCare digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch client notes
ShiftCare
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
ShiftCare
Queued
Collections and dashboards
ShiftCare health computed on a schedule.
Four metrics, 14 days of records created and a team breakdown, no model involved.
ShiftCare health
Refreshed 4 minutes ago · every 15 minutes · from the client notes collection
Client notes
1,284 ↓ 12%
Complaints
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Client notes created
Last 14 days
By team
Share of activity
Rostering 34%
People and HR 27%
Quality 21%
Care Coordination North 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect ShiftCare to Claude?
First, add ShiftCare in Elaichi. ShiftCare connects with an API key, so you copy the key from your ShiftCare account and paste it into Elaichi, and there is 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. Sign in with your Elaichi account and ShiftCare is ready to use inside Claude.
Does ShiftCare work with ChatGPT and Cursor as well as Claude?
Yes. Once ShiftCare 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 ShiftCare once and every client you use picks it up.
What can an AI agent actually do with my ShiftCare data?
An agent connected to ShiftCare can list, create and update shifts, add and edit client notes, record and update staff leave, log complaints and update them in bulk, and look up your locations, areas, facilities and teams. It can also attach reference numbers from other systems to ShiftCare records. Because ShiftCare offers a large set of actions, the agent searches for the right one as you ask, so short direct requests such as "list tomorrow's unfilled shifts at Riverside" work better than long paragraphs.
Does connecting ShiftCare give the AI access to every client and every roster?
No. Each person signs in to Elaichi as themselves, so an agent working in ShiftCare on their behalf can only reach the clients, shifts and staff records that person's own ShiftCare access allows. Elaichi can narrow that further, for example to read-only or to a subset of actions, but it can never widen it beyond what the person already has.
Can I stop an agent from deleting or changing things in ShiftCare?
Yes. In Elaichi, restrictions on ShiftCare apply per action, so you can allow reading shifts and leave while blocking the creation or editing of client notes, complaints or rosters. A blocked action is never shown to Claude, ChatGPT, Cursor or any other client at all, so no prompt, however worded, can reach it.
What happens to a ShiftCare connection when someone leaves?
When a person is offboarded in Elaichi, their access to ShiftCare through every connected client ends at once, and the audit log keeps a record of everything they did while they had it. If they had shared a ShiftCare connection with a team, that connection keeps working for everyone else. If you want to remove ShiftCare altogether, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Put ShiftCare in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.