ShiftCare MCP connector
The ShiftCare connector brings shifts, client notes, staff leave, complaints, teams and facilities into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so care coordinators can ask questions and update rosters as themselves, with every action recorded.
- Connects with an API key
- Free 14-day trial
- No credit card
List all open ShiftCare complaints raised this week.
Working in ShiftCare with Elaichi
-
List all ShiftCare account locations
-
List all ShiftCare areas
-
List all ShiftCare complaints
How to connect ShiftCare to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
ShiftCare 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.
ShiftCare 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.
ShiftCare 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.
ShiftCare 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.
ShiftCare 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 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.
What teams do with ShiftCare through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in ShiftCare is logged.
-
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.”
What connecting ShiftCare gets you
6 screens from Elaichi, each doing one job for your ShiftCare account.
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, Cursor or Microsoft Copilot
The agent
Ask about shifts, get answers from ShiftCare.
Type a question in plain language and read live client notes, leaves and complaints.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach ShiftCare here.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
98 ShiftCare tools ready without custom code.
Browse tool names, resources and methods across clients, leaves, complaints and areas.
Toolboxes
Every team gets its own ShiftCare toolbox.
Rostering, HR and quality each see a curated set of ShiftCare tools.
Shared connections
Share a ShiftCare account, never the credential.
See who connected each account and how many teams and members use it.
Audit log
Every ShiftCare call is written down.
When, who, what happened, type and resource, in an append only log.
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.
ShiftCare digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
ShiftCare
Queued
Automations
A schedule fires, ShiftCare work gets done.
Six steps fetch leaves, group them, draft a digest, await approval, then post back.
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%
Collections and dashboards
ShiftCare health computed on a schedule.
Four metrics, 14 days of records created and a team breakdown, no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for ShiftCare
All three can connect ShiftCare 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 ShiftCare tools | Allow or restrict single ShiftCare 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 ShiftCare 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.
ShiftCare tools for your AI agents
98 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.
Questions, answered
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, Microsoft Copilot, 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 restricting the creation or editing of client notes, complaints or rosters. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot and every other client.
Does the ShiftCare MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. ShiftCare 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 ShiftCare?
Yes. Both let Claude, ChatGPT or Cursor use ShiftCare. 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 ShiftCare call.
How is Elaichi different from Composio for ShiftCare?
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 ShiftCare: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put ShiftCare 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