Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect 7shifts to Claude Code

Let Claude build schedules and approve time-off in 7shifts. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect 7shifts to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect 7shifts, you add a 7shifts MCP server: a small hosted service that exposes 7shifts's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own 7shifts account. No API keys pasted into config files.

claude mcp add --transport http 7shifts https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in 7shifts once connected?

Full read-write 7shifts access lets Claude draft a weekly schedule, assign shifts to available staff, approve or decline time-off requests, create calendar events for a company, and adjust open shifts once you approve. The schedule building that used to mean clicking through every cell happens where the roster already lives.

  • Draft a weekly schedule and assign shifts based on staff availability
  • Approve, decline, or update time-off requests
  • Create or edit open shifts and publish them to a location
  • Create a calendar event for a company or location
  • Update a staff member's role, wage, or assigned department
  • Find understaffed shifts across locations and propose coverage

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same 7shifts access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the 7shifts API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when 7shifts changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build 7shifts connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same 7shifts connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own 7shifts account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on 7shifts's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to 7shifts?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the 7shifts account it signs in with. Revoking access is one click in 7shifts.

More on the 7shifts connector

7shifts connector for claude.aiMyCase + Claude CodePracticePanther + Claude CodeFilevine + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us