7shifts for AI agents
7shifts is scheduling and workforce software for restaurants, covering shift planning, time clocking and staff communication. Managers and owners use it to run daily labor operations. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in 7shifts.
List upcoming shifts
Pull the shift schedule for a location so a manager can see who is on the floor this week.
Update a department record
Rename a department or adjust its settings, a write action that gets logged and is easy to review.
Delete a department
Remove a department from the account, a destructive action that should be flagged for approval before it runs.
10 7shifts actions, graded by risk.
Every 7shifts action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
7Look things up. Allowed by default.
- 7shifts.list_usersList Users
- 7shifts.list_shiftsList Shifts
- 7shifts.get_departmentGet Department
- 7shifts.list_companiesList Companies
- 7shifts.list_locationsList Locations
- 7shifts.list_departmentsList Departments
- 7shifts.get_user_assignmentsGet User Assignments
write
2Create and change things. Allow, or ask the user first.
- 7shifts.create_departmentCreate Department
- 7shifts.update_departmentUpdate Department
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- 7shifts.delete_departmentDelete Department
7shifts in three steps.
- 01Your users connect 7shiftsThey add their 7shifts api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Department” can wait for the user, and “delete Department” can be denied outright.
- 03Any agent can actYour agent calls 7shifts through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('7shifts', { read: 'allow', write: 'ask', // create_department destructive: 'deny', // delete_department }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How 7shifts connects.
Users add their 7shifts api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same 7shifts connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use 7shifts from any agent.
7shifts and Arc0, answered.
Can I use 7shifts with Claude, ChatGPT or Cursor?
Yes. Connect 7shifts to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the 7shifts actions you allow.
How do users connect 7shifts?
Users add their 7shifts api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which 7shifts actions can my agent take?
10 in total: 7 read, 2 write and 1 destructive, such as “create Department”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in 7shifts?
Yes. Actions like “delete Department” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call 7shifts too?
Yes. The same 7shifts connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug 7shifts into your agent.
Your users connect 7shifts once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan