7shifts logoMCP server · People and HR

7shifts MCP server

7shifts in any MCP client, through Memtro: 7shifts does not publish this server. Memtro's 7shifts connector reads 7shifts through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

7shifts restaurant scheduling: employees, the published and draft schedule (shifts by location, person and date), time punches with hours worked, time-off requests, locations, departments and roles; when you ask, can create, change and delete shifts and time punches, approve, decline or delete time off, add an employee and deactivate one.

Reads

  • sevenshifts_list_usersEmployees and managers in 7shifts: name, type (employee, manager, asst_manager, employer), active, invite status and employee id.
  • sevenshifts_list_shiftsThe schedule: shifts starting in a window (default today to seven days ahead), with person, start and end, location, department, role, station…
  • sevenshifts_list_time_punchesTime punches (clock-ins) in a window (default the last seven days): person, shift, location, role, clocked in and out, hours, breaks, approved…
  • sevenshifts_list_time_offTime-off requests: person, from and to dates, partial-day times, hours and the status code 7shifts returns (its meanings are not documented).
  • sevenshifts_list_locationsThe company's 7shifts locations (restaurants): id, name, city, state, country and timezone.
  • sevenshifts_list_departmentsDepartments (front of house, kitchen…) per location: id, name, location id and whether it is the default.
  • sevenshifts_list_rolesRoles (server, line cook…) per location and department: id, name, job code, and whether tipped.

Acts, when you ask

These change something in 7shifts. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • sevenshifts_create_shiftCreates a shift in 7shifts at a location for a person (user_id) or as an open shift anyone eligible can request.
  • sevenshifts_update_shiftChanges a 7shifts shift: who works it, its times, location, department, role, notes, or whether it is a draft (draft false publishes the change).
  • sevenshifts_delete_shiftPermanently deletes a 7shifts shift; it leaves the schedule the employee sees.
  • sevenshifts_create_time_punchAdds a time punch (a clock-in, and clock-out if given) for an employee at a location; it counts toward their hours and payroll.
  • sevenshifts_update_time_punchCorrects a 7shifts time punch: clock-in or clock-out time, department, role or notes; the employee's hours and payroll change with it.
  • sevenshifts_delete_time_punchPermanently deletes a 7shifts time punch; its hours leave the employee's timesheet and payroll.
  • sevenshifts_approve_time_offApproves a time-off request in 7shifts, with an optional message to the employee (7shifts does not document whether they are notified).
  • sevenshifts_decline_time_offDeclines a time-off request in 7shifts, with an optional message to the employee (7shifts does not document whether they are notified).
  • sevenshifts_delete_time_offPermanently deletes a time-off request in 7shifts.
  • sevenshifts_create_userAdds an employee (or manager) to 7shifts at the locations and departments given, which gives them access to the schedule.
  • sevenshifts_deactivate_userDeactivates a 7shifts employee: they lose access and leave the schedule.

Connect it

First connect 7shifts on Dashboard → Connections, then add Memtro to your client once. The 7shifts tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared 7shifts connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › Who is on the schedule at the downtown location this weekend?
  • › How many hours did the kitchen team clock last week?
  • › Which time-off requests end after next Monday?
  • › Are there any open shifts on Saturday?
  • › Approve Tom Reilly's time-off request for next Friday.

Questions

Is this an official 7shifts MCP server?
No. It is Memtro's MCP server with Memtro's 7shifts connector behind it: the connector reads 7shifts through its API with the credentials you connect on Dashboard → Connections, and 7shifts publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in 7shifts?
Only when you ask, and only what it has been granted: create a shift, as a draft or on the published schedule; change a shift; delete a shift (permanent); add a time punch for an employee; correct a time punch; delete a time punch (permanent); approve a time-off request; decline a time-off request; delete a time-off request (permanent); add an employee, and invite them if you ask; deactivate an employee. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · People and HR

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time