Read RotaCloud shifts, attendance, leave, availability and payroll; create shifts and handle leave. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"rotacloud": {
"url": "https://rotacloud.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"rotacloud": {
"type": "http",
"url": "https://rotacloud.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your RotaCloud API key.
Create one in RotaCloud → Settings → Integrations → API (an account admin can do this; available on all plans). Calls run with admin permissions. Your key is used only to call the RotaCloud API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your RotaCloud API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the RotaCloud connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
rotacloud_list_accounts | read | List accounts The RotaCloud account(s) this API key belongs to: name, plan, time zone, employee count. GET /accounts. |
rotacloud_list_users | read | List users 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. |
rotacloud_get_user | read | Get user One employee by id. GET /users/{id}. |
rotacloud_list_locations | read | List locations List locations (sites/branches) with address, time zone and managers. GET /locations. |
rotacloud_list_roles | read | List roles List job roles (positions) with colour, default break and pay rate. GET /roles. |
rotacloud_list_shifts | read | List shifts 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. |
rotacloud_get_shift | read | Get shift One shift by id. GET /shifts/{id}. |
rotacloud_list_swap_requests | read | List shift swap requests List shift swap requests with their status, the shifts and the users involved. GET /swap_requests. |
rotacloud_list_day_notes | read | List day notes List day notes (notices pinned to rota dates, e.g. events or deliveries), optionally for one location. GET /day_notes. |
rotacloud_list_attendance | read | List attendance records List time & attendance records (clock-in/out times, breaks, minutes late, hours, approval state) in a time range. GET /attendance. |
rotacloud_list_clocked_in | read | List clocked-in users Who is clocked in right now: user, location, role, clock-in time, minutes late and break state. GET /users_clocked_in. |
rotacloud_list_leave | read | List leave 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. |
rotacloud_list_leave_requests | read | List leave requests List leave requests awaiting a decision (and past ones): user, leave type, dates, half days, the employee's message. GET /leave_requests. |
rotacloud_get_leave_request | read | Get leave request One leave request by id, with the per-day breakdown. GET /leave_requests/{id}. |
rotacloud_list_leave_types | read | List leave types List leave types (Holiday, Sickness, Unpaid, ...) with id, short name and whether employees can request them. GET /leave_types. |
rotacloud_list_holiday_allowances | read | List holiday allowances Every employee's holiday allowance for a leave year (default and custom allowance, unit, carried over). GET /holiday_allowances/{year}. |
rotacloud_get_availability | read | Get availability Employees' availability per date in a range (available / unavailable times). GET /availability. |
rotacloud_list_days_off | read | List days off Employees' scheduled days off per date in a range. GET /days_off. |
rotacloud_list_pay_periods | read | List pay periods List pay periods overlapping a date range (id, name, start/end date, locked). GET /pay_periods. |
rotacloud_get_payroll | read | Get payroll for a pay period 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. |
rotacloud_create_shift | write | Create shift 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. |
rotacloud_update_shift | write | Update shift WRITE: change a shift's times, assignee, location, role, break, notes or published state. Only the fields you pass change. POST /shifts/{id}. |
rotacloud_publish_shifts | write | Publish shifts WRITE: publish shifts so the assigned employees see them (and get notified). POST /shifts_published. |
rotacloud_create_leave_request | write | Request leave 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. |
rotacloud_approve_leave_request | write | Approve leave request WRITE: approve a pending leave request (it becomes booked leave and the employee is notified). POST /leave_requests/{id}/approve. |
rotacloud_deny_leave_request | write | Deny leave request WRITE: deny a pending leave request (the employee is notified). POST /leave_requests/{id}/deny. |
rotacloud_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
rotacloud_request_feature | Request a missing feature Tell usefulapi that the user needs something the RotaCloud tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
rotacloud_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on RotaCloud (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
rotacloud_cancel_subscription | Cancel the Pro subscription Cancel the caller's RotaCloud Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run rotacloud_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper account | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this RotaCloud server only. Subscribe with rotacloud_upgrade (it returns a Stripe Checkout link). Cancel any time with rotacloud_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running rotacloud_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by RotaCloud. The server calls the RotaCloud API with your own RotaCloud access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your RotaCloud API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your RotaCloud API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the RotaCloud API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in RotaCloud.
Yes, if you approve it. 6 of the 26 RotaCloud tools can create or change data. The other 20 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this RotaCloud server only. Cancel any time: Pro then runs to the end of the paid period. Run rotacloud_usage_status to see how many calls you used.
Ask the AI to run rotacloud_upgrade: it returns a Stripe Checkout link. To cancel, run rotacloud_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with rotacloud_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.