RotaCloud MCP by usefulapi

WRITE: approve a pending leave request (it becomes booked leave and the employee is notified). POST /leave_requests/{id}/approve.

WRITE: submit a leave request on behalf of an employee (sent as that user, for a manager to approve). POST /leave_requests with the User header.

WRITE: create a shift on the rota. Leave user_id out for an open shift. Unpublished by default (employees see it once published). POST /shifts.

WRITE — deletes shifts from the rota (assigned employees lose the shift). Delete 1-100 shifts by id; select them first with rotacloud_find_shifts. Without confirm it only previews: it reads each shift and deletes nothing. Show the preview to the user, then call again with confirm: true. Guards re-check each shift right before its delete and skip it if it no longer qualifies: require_open (skip assigned shifts), require_shorter_than_minutes (skip shifts whose elapsed duration is not strictly less). After each delete the shift is read again to verify it is gone. DELETE /shifts/{id}.

WRITE: deny a pending leave request (the employee is notified). POST /leave_requests/{id}/deny.

Find shifts in a time range by open/assigned state, published state, location, role and ELAPSED duration (end − start; the break is not subtracted). It reads page after page, so it is the way to select shifts for a bulk change such as rotacloud_delete_shifts: e.g. open shifts shorter than 3 hours = open: true, shorter_than_minutes: 180 (a shift of exactly 180 minutes does not match). Deleted shifts never match. Returns up to max_results matches (shift_ids plus a summary each: UTC times, elapsed_minutes, user, location, role, published). complete: true = the whole range was read. Otherwise pass next_offset as offset to continue — but after deleting or changing shifts, search again from offset 0, because the list positions move. GET /shifts.

Employees' availability per date in a range (available / unavailable times). GET /availability.

One leave request by id, with the per-day breakdown. GET /leave_requests/{id}.

Payroll for one pay period, per employee: pay settings, attendance worked, paid/unpaid leave, overtime and pay totals. Contains pay data. GET /pay_periods/{id}/payroll.

One shift by id. GET /shifts/{id}.

One employee by id. GET /users/{id}.

The RotaCloud account(s) this API key belongs to: name, plan, time zone, employee count. GET /accounts.

List time & attendance records (clock-in/out times, breaks, minutes late, hours, approval state) in a time range. GET /attendance.

Who is clocked in right now: user, location, role, clock-in time, minutes late and break state. GET /users_clocked_in.

List day notes (notices pinned to rota dates, e.g. events or deliveries), optionally for one location. GET /day_notes.

Employees' scheduled days off per date in a range. GET /days_off.

Every employee's holiday allowance for a leave year (default and custom allowance, unit, carried over). GET /holiday_allowances/{year}.

List booked leave (holiday, sickness, etc.) with type, user, dates, hours and status. Filter by date range or leave year, users and leave types; pending/denied/expired requests are excluded unless asked for. GET /leave.

List leave requests awaiting a decision (and past ones): user, leave type, dates, half days, the employee's message. GET /leave_requests.

List leave types (Holiday, Sickness, Unpaid, ...) with id, short name and whether employees can request them. GET /leave_types.

List locations (sites/branches) with address, time zone and managers. GET /locations.

List pay periods overlapping a date range (id, name, start/end date, locked). GET /pay_periods.

List job roles (positions) with colour, default break and pay rate. GET /roles.

List rota shifts in a time range: start/end times (Unix seconds), break, assigned user (null = open shift), location, role, notes, published and acknowledged state. Filter by users, locations, roles, open or published. GET /shifts.

List shift swap requests with their status, the shifts and the users involved. GET /swap_requests.

List employees (users) with their level, roles, locations, contact details and pay settings. Use it to map user ids in shifts, leave and attendance to names. GET /users.

WRITE: publish shifts so the assigned employees see them (and get notified). POST /shifts_published.

WRITE: change a shift's times, assignee, location, role, break, notes or published state. Only the fields you pass change. POST /shifts/{id}.