Claude + 7shifts: Official MCP Server Setup and Limits
Short answer: yes. 7shifts now publishes its own official MCP server, and Claude can connect to it. The server lives at https://developers.7shifts.com/mcp, and 7shifts’ docs describe adding it in Claude as a custom connector. Two limits matter for a restaurant. The server is read-only: Claude can look up schedules, time punches, and labor, but it can’t publish a schedule, edit a punch, or change anything. And Claude still has no event triggers. It answers when you ask, or on a timer you set. It can’t watch your schedule and react to a call-out.
Here’s the plain-English version: what’s possible, what it takes, where it stops, and what to use if you want 7shifts work to happen without you babysitting a chat window.
How to connect Claude to 7shifts
7shifts documents the setup on its developer site:
- In Claude, open Customize → Connectors (7shifts’ docs call it Settings → Connectors) and choose Add custom connector.
- Paste
https://developers.7shifts.com/mcpand save. - Ask Claude what the 7shifts API can tell you about schedules to confirm it’s connected.
Without credentials, that connection reads 7shifts’ API spec and documentation. That helps you check whether a workflow is possible, but it isn’t your restaurant’s data. To read live schedules, punches, wages, and employee records, the server needs an access token sent as a Bearer header. You create one in 7shifts under Company Settings → Developer Tools. 7shifts’ example puts that header in an MCP config file, the format Claude Code and similar tools use.
Two things to know before you add a token:
- It’s admin-level. 7shifts warns that a token reads real wage data, employee records, and time punches, there’s no sandbox, and that data enters Claude’s context.
- Read-only is deliberate. 7shifts blocks every write through MCP because a changed punch or a published schedule hits real payroll. Claude can draft code for a write, but nothing changes in 7shifts from the chat.
For simple no-code hand-offs, 7shifts is also on Zapier, with triggers like schedule published, time punch created, and payroll period closed. That’s a different thing from a chat assistant.
What the Claude + 7shifts connection actually does
Once the connector has a token, what you get is a smart assistant inside a chat window: you ask, it answers. You could say “pull next week’s published schedule from 7shifts and tell me who’s over 40 hours,” or “summarize last week’s time punches and flag anyone who clocked in late three times,” and it would. That’s genuinely useful for looking things up and drafting from your labor numbers.
What you would not get is anything that reacts to your restaurant — and in a business run on call-outs and no-shows, that’s the part that matters.
The limit that matters: Claude has no event triggers
ChatGPT can start a task from an event, but only when the app's plugin supports it. OpenAI documents three: a new Gmail message, a new Slack message and GitHub pull request activity. On September 29, 2026 it said other supported plugins can start automations too, without publishing which. Claude's scheduled tasks still run on a clock alone. A deal moving, a form coming in, an invoice clearing: neither one promises to wake up for any of it. Carly watches all of them, across the thousands of apps it connects to.
For a restaurant, that has three consequences worth being blunt about:
- It never notices anything. Claude can’t see that a server just called out for tonight’s dinner shift, or that Saturday is suddenly short two line cooks, and do something about it. Nothing moves until you ask, or until the next scheduled run comes around.
- The clock is the trigger, not the call-out. Claude pulls a schedule when the timer says to. It doesn’t sit on your labor targets watching for overtime creep — and dinner service doesn’t wait for the top of the hour.
- A schedule can’t cover a shift. A Cowork task that runs each morning still finds last night’s call-out tomorrow. There’s no “when someone drops a shift, do this,” and no inbox of its own to receive work.
What about email — can’t Claude just message the team? Out of the box, no: Claude’s Gmail connector asks you to approve every send, and its Outlook add-in doesn’t send at all — the last click is still yours. A developer could build sending in too, but that’s one more thing to wire up and maintain, and nothing sets it off the moment a shift opens up.
And note that 7shifts already has its own AI built in: the machine-learning Auto-Scheduler that factors in guest flow and labor targets, plus an AI Schedule Importer that turns an existing schedule file into a new account’s setup (trial accounts only). Claude isn’t replacing those; it’s a general assistant you’d point at your data.
Claude with the official connector is great for “help me pull and read this,” and simply not built for “cover every call-out and keep me under my labor target automatically.”
If you want 7shifts work to happen on its own: Carly
The moment you want something to happen around 7shifts the second it happens — a manager pinged the moment the schedule goes over budget, a call-out that triggers a cover request, a Monday-morning labor recap — you’ve walked past what Claude is for.
Carly connects to 7shifts with the same admin access token, pasted at carlyassistant.com/integrations under Custom API Keys. Then Carly runs the actual work for you, 24/7 in the cloud, across your inbox, calendar, and thousands of other apps:
- When a shift goes unclaimed 48 hours out, Carly emails the eligible staff and asks who can pick it up — then flags the manager if no one bites.
- When the published schedule pushes labor over your target, Carly sends the GM a heads-up with the offending days, before payroll locks.
- When a new hire is added in 7shifts, Carly sends the welcome note and onboarding checklist on its own.
- Every Monday, Carly rolls last week’s punches and labor cost into one recap and emails it to owners on schedule.
Claude reads your 7shifts data in a chat, and the official server keeps it at “read.” Carly takes that same token and acts on it: it acts on its own when an email arrives, runs on a schedule, drafts and sends across Gmail and Outlook, updates records, and manages tasks. AI agents start at $35/month.
Claude vs Carly for 7shifts
| Claude (official 7shifts connector) | Carly | |
|---|---|---|
| Look up schedules & summarize labor | Yes | Yes |
| Acts the moment something happens (call-out, over-budget schedule) | No | Yes |
| Chases unclaimed shifts on its own | No | Yes |
| Runs on event triggers | No | Yes (cloud) |
| Sends the emails itself, not just drafts | No, every send waits on your approval | Yes |
| What it takes to set up | Add the 7shifts connector, plus an admin token for live data | Paste your 7shifts token |
| Pricing | Claude Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude is a 7shifts lookup you ask, or put on a timer. Carly is a teammate that acts on call-outs, overtime, and labor targets the moment they happen.
Frequently Asked Questions
Does Claude work with 7shifts?
Yes. 7shifts publishes an official, read-only MCP server at https://developers.7shifts.com/mcp that you add in Claude as a custom connector. To read live schedules and punches, it needs an admin access token from Company Settings → Developer Tools, sent as a Bearer header. Like everything Claude, it has no event triggers: you ask, or a scheduled task asks on a clock.
How do I get a 7shifts API token?
In 7shifts, go to Company Settings → Developer Tools and create an access token for your own account. (Outside software companies use 7shifts’ OAuth flow instead; the old “API key” method was retired in 2022.) 7shifts’ official MCP server uses that token for live reads, and Carly takes the same token under Custom API Keys.
Can Claude send my staff their shifts automatically?
No. Claude’s Gmail connector asks you to approve every send and its Outlook add-in doesn’t send at all, and nothing fires when a shift opens up — a scheduled task runs on a clock, not on the drop. That automatic, on-its-own work is what Carly is built for.
What if I want 7shifts to act on its own — chase cover, warn me on overtime?
That’s beyond what Claude does; it answers on request or on a timer, and doesn’t act on events. Carly connects with your 7shifts token and runs on triggers and schedules 24/7 in the cloud — it can email staff, flag over-budget schedules, and send labor recaps without you. AI agents start at $35/month.
More: Claude connectors · Claude + Deputy · Claude + Toast POS · Best AI tools for restaurants · Can Claude send emails · Claude vs Carly · Best AI automation tools for 7shifts
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
