7shifts MCP connector
Connecting 7shifts to Elaichi lets Claude, ChatGPT, Cursor and any MCP client look up and update your 7shifts locations, departments, roles and team members, with every person signed in as themselves and every change 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 7shifts to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect 7shifts once
-
Open Connections, choose Add connection, and pick 7shifts.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste your 7shifts app credentials. 7shifts 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.
7shifts 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.
7shifts 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 today. The plugin directory lives at chatgpt.com/plugins.
7shifts 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.
Connect 7shifts 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 7shifts through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Operations
Open a new location in minutes
When a new restaurant comes online, describe it once and have the location created in 7shifts with its departments and roles set up to match your other sites.
-
HR
Add new hires to 7shifts as they start
Paste in a new hire's details after the offer is signed and have their 7shifts account created and placed in the right location, department and role.
-
General managers
Check who works where before scheduling
Ask which team members are assigned to the front of house at a given location, or which roles a site still has open, and get the answer from the live 7shifts roster.
-
Multi-unit leaders
Keep roles consistent across every site
Compare the departments and roles set up at each 7shifts location and fix the ones that drifted, so a server means the same thing in every store.
-
Payroll
Review labor settings before the pay run
Pull up the labor settings and inactive reasons configured for the company in 7shifts and confirm they match your policy before approving payroll.
-
Franchise support
Audit company details across the brand
List every company and location connected to your 7shifts account, spot missing addresses or outdated details, and update them without opening each one by hand.
Try asking
- “Show open shifts at the downtown location this week.”
- “List departments with the most schedule conflicts today.”
- “Which locations have inactive employees pending review.”
Compare
Elaichi vs Zapier MCP vs Composio for 7shifts
All three can connect 7shifts 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 7shifts tools | Allow or restrict single 7shifts 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 7shifts 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 | $15 per user per month. | 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.
AI tools
7shifts tools for your AI agents
146 tools are ready to call through Elaichi's MCP endpoint the moment you connect 7shifts, 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 7shifts gets you
6 screens from the product, each doing one job for your 7shifts account.
The agent
Ask 7shifts questions, get scheduling answers instantly.
Type a question in plain language and pull live shift and location data from 7shifts.
- shifts
- locations
- departments
- companies
Ask Elaichi to work across your apps.
Show open shifts at the downtown location this week.
List departments with the most schedule conflicts today.
Which locations have inactive employees pending review.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One 7shifts endpoint, every client connects.
Claude, ChatGPT and Cursor reach 7shifts through a single governed endpoint, no shared keys.
Copy the endpoint
Tool catalog
146 7shifts tools, zero custom code.
Every 7shifts method, resource and endpoint is cataloged and ready to call.
- List all 7shifts whoami
- 7shifts partner company create trial account
- List all 7shifts companies
- Get single 7shifts company by ID
Toolboxes
Every team gets its own 7shifts toolbox.
Scheduling, payroll and operations each work from a toolbox scoped to their team.
- Scheduling
- Payroll
- Operations
- HR
Shared connections
Delegated 7shifts access, no shared passwords.
See who connected each 7shifts account and how many teams work through it.
- Downtown
- Airport Location
- Warehouse Ops
- Retail East
Audit log
Every 7shifts call, logged and attributable.
See who ran what against 7shifts, when it happened and what 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
7shifts schedules trigger real approved work.
A schedule fires, records are fetched and grouped, a draft is approved, then posted back.
7shifts digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch shifts
7shifts
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
7shifts
Queued
Collections and dashboards
7shifts health, computed on a schedule.
Four metrics and a 14 day chart of records created, broken down by team.
7shifts health
Refreshed 4 minutes ago · every 15 minutes · from the shifts collection
Shifts
1,284 ↓ 12%
Locations
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Shifts created
Last 14 days
By team
Share of activity
Downtown 34%
Airport Location 27%
Warehouse Ops 21%
Retail East 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect 7shifts to Claude?
Connect 7shifts in Elaichi first: 7shifts uses app credentials, so you sign in by entering the access credentials from your 7shifts account, and there is no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste in the endpoint https://api.elaichi.ai/mcp. Sign in when Claude asks, and your 7shifts locations, roles and team members are available in the conversation.
Does 7shifts work with ChatGPT and Cursor as well as Claude?
Yes. Once 7shifts 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 7shifts once and every client you use picks it up.
What can an AI agent actually do with my 7shifts data?
With 7shifts connected, an agent can list your companies, locations, departments, roles and team members, look up any one of them, and create or update locations, departments, roles and users when you ask. It can also read your company's labor settings and inactive reasons. Because 7shifts exposes a lot of actions, short and specific asks like "add a new server at the Main Street location" work better than long paragraphs.
Does connecting 7shifts give the AI access to every location and employee?
No. The AI only sees what the person who signed in to 7shifts can already see, so a manager limited to one location stays limited to that location. Elaichi can narrow that access further, for example to read-only, but it can never widen it beyond what 7shifts itself allows that person.
Can I stop an agent from deleting or changing things in 7shifts?
Yes. Restrictions in Elaichi apply per action, so you can allow looking up 7shifts locations and team members while blocking the ability to delete a location, department or role, or to update anything at all. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it.
What happens to a 7shifts connection when someone leaves?
When you offboard a person in Elaichi, their access to 7shifts through every AI client ends at once. If they had shared a 7shifts connection with a team, it keeps working for everyone else. If you want to remove 7shifts entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the 7shifts MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. 7shifts 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, 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 7shifts?
Yes. Both let Claude, ChatGPT or Cursor use 7shifts. 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 7shifts call.
How is Elaichi different from Composio for 7shifts?
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 7shifts: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put 7shifts in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.