RotaCloud MCP server

What the model can do

RotaCloud staff rotas: employees with roles and locations, shifts in a date window (who, where, which role, when), booked leave and pending leave requests, locations, roles and day notes. Can create, change, delete, publish and unpublish shifts, approve or deny leave and unavailability requests, book and delete leave, message staff, add, edit or delete manager-only day notes, and add or delete employees. Pay and personal details are never read or set.

Reads

• rotacloud_list_usersEmployees in RotaCloud: name, email, permission level, roles, locations and start and final working dates.
• rotacloud_list_shiftsShifts in a date window (default today for 7 days, at most 31): employee, location, role, start and end (UTC, with the location's time zone)…
• rotacloud_list_leaveBooked leave overlapping a date window (default today for 14 days, at most 31): employee, leave type, status and dates with half days.
• rotacloud_list_leave_requestsLeave requests waiting for a decision: employee, leave type and dates.
• rotacloud_list_locationsLocations (sites) in RotaCloud with their time zones.
• rotacloud_list_rolesRoles (job types shifts are rota'd as, e.g. Barista, Supervisor) with how many employees hold each.
• rotacloud_list_day_notesDay notes on the rota in a date window (default today for 14 days, at most 31): dates, locations, title, message and whether staff can see it.

Acts, when you ask

These change something in RotaCloud. 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.

• rotacloud_add_day_noteAdds a day note to the RotaCloud rota for one or more locations and a date or date range, as the API key (an administrator).
• rotacloud_update_day_noteChanges the given fields of one RotaCloud day note: dates, locations, title or message.
• rotacloud_delete_day_notePermanently deletes one RotaCloud day note.
• rotacloud_create_shiftCreates one RotaCloud shift at a location, for an employee or as an open (unassigned) shift.
• rotacloud_update_shiftChanges the given fields of one RotaCloud shift: times, employee, location, role, break or notes.
• rotacloud_delete_shiftPermanently deletes one RotaCloud shift.
• rotacloud_publish_shiftsPublishes named RotaCloud shifts, so the employees on them see them on their rota; RotaCloud may notify them.
• rotacloud_unpublish_shiftsUnpublishes named RotaCloud shifts, taking them off the employees' rotas back to draft.
• rotacloud_approve_leave_requestApproves one pending RotaCloud leave request (from rotacloud_list_leave_requests): it becomes booked leave, uses the employee's allowance…
• rotacloud_deny_leave_requestDenies one pending RotaCloud leave request; the employee sees the decision and any message.
• rotacloud_create_leaveBooks approved leave of one type for named employees between two dates (with half days), using their allowance.
• rotacloud_delete_leavePermanently deletes one RotaCloud leave record (from rotacloud_list_leave), taking the leave off the rota.
• rotacloud_approve_unavailabilityApproves one RotaCloud unavailability request; the employee sees the decision and any message.
• rotacloud_deny_unavailabilityDenies one RotaCloud unavailability request; the employee sees the decision and any message.
• rotacloud_send_messageSends a message through RotaCloud to named employees (it reaches them in RotaCloud and by email), from the account.
• rotacloud_create_userAdds an employee to RotaCloud with their name, email, permission level, locations and roles.
• rotacloud_delete_userDeletes one employee from RotaCloud, removing their access.

Connect it

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

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

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

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

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 RotaCloud 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 working at Soho on Saturday?
• › Which shifts next week are still open?
• › Which leave requests are waiting for a decision?
• › Approve Jo Bell's holiday request for the first week of June.
• › Create an open bar shift at Soho on Friday from 6pm to midnight and publish it.

Questions

Is this an official RotaCloud MCP server?

No. It is Memtro's MCP server with Memtro's RotaCloud connector behind it: the connector reads RotaCloud through its API with the credentials you connect on Dashboard → Connections, and RotaCloud 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 RotaCloud?

Only when you ask, and only what it has been granted: add a day note for managers to a rota day; edit or delete a day note; create, change or delete a shift; publish or unpublish named shifts (staff see published shifts); approve or deny a leave request; book leave for named employees, or delete a leave record; approve or deny an unavailability request; send a message to named employees; add an employee, optionally sending the invite; delete 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 · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server