Read staff, locations, shifts, gaps and leave; create leave requests in Rotageek. For rota managers who plan shifts, cover and leave for staff in Rotageek. 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": {
"rotageek": {
"url": "https://rotageek.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"rotageek": {
"type": "http",
"url": "https://rotageek.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.
List the locations, then read the schedule of one location for a date-time window, with every user there.
rotageek_list_locations rotageek_list_location_schedule
List the open gaps, which are unfilled shifts, for one or more locations between two date-times.
rotageek_list_locations rotageek_list_gaps
List the leave requests in a date range, with the leave types, to plan cover.
rotageek_list_leave_requests rotageek_list_leave_types
Find the user and the leave type. Create a leave request with a start and end date-time. It can change the rota and the holiday balance.
Changes data · rotageek_list_users rotageek_list_leave_types rotageek_create_leave_request
Read the scheduled and worked hours of each user at one location for the week that starts on a given date.
rotageek_get_timesheet
The login page asks for your Rotageek API username and Rotageek API user password.
Your Rotageek admin creates the API user, or asks Rotageek Customer Success to set one up. Use that user's username and password. The password is used only to request an access token from Rotageek.
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 Rotageek API username and Rotageek API user password. 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 Rotageek connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
rotageek_list_users | read | List users List the users (staff) in the organisation, optionally filtered by user ids or a location. Use it first to find the user ids the other tools need. Rotageek API: GET /api/v1/users. |
rotageek_get_user | read | Get a user Get one user by id: name, contact details, primary location and status. Rotageek API: GET /api/v1/users/{userId}. |
rotageek_list_locations | read | List locations List the locations (sites) of the organisation. Rotageek API: GET /api/v1/locations. |
rotageek_get_location | read | Get a location Get one location by id, with its settings. Rotageek API: GET /api/v1/locations/{locationId}. |
rotageek_list_location_users | read | List users at a location List the users assigned to one location. Rotageek API: GET /api/v1/locations/{locationId}/users. |
rotageek_list_user_shifts | read | List a user's schedule List the scheduled shifts and leave records of one user between two date-times, with start, end, location and break minutes. Rotageek API: GET /api/v1/schedule/users/{userId}. |
rotageek_list_location_schedule | read | List a location's schedule List the scheduled shifts and leave records of one location between two date-times, for every user there. Rotageek API: GET /api/v1/schedule/locations/{locationId}. |
rotageek_list_gaps | read | List open gaps List the open gaps (unfilled shifts) for one or more locations between two date-times. Rotageek API: GET /api/v1/gaps/locations. |
rotageek_list_leave_requests | read | List leave requests List the leave requests of the organisation, optionally in a leave year or date range. Rotageek API: GET /api/v1/leave/requests. |
rotageek_list_leave_types | read | List leave types List the leave types (for example holiday or sickness) and their ids. Rotageek API: GET /api/v1/leave/types. |
rotageek_create_leave_request | write | Create a leave request Create a leave request for one user with a leave type id and a start and end date-time. It is saved in Rotageek and can change the rota and holiday balance. Rotageek API: POST /api/v1/leave/requests/users/{userId}. |
rotageek_get_timesheet | read | Get a week's timesheet Get the timesheet records of one location for the week that starts on weekStartDate: hours scheduled and worked per user. Rotageek API: GET /api/v1/timesheets/locations/{locationId}/{weekStartDate}. |
rotageek_list_positions | read | List positions List the job positions (roles) of the organisation with their ids. Rotageek API: GET /api/v1/positions. |
rotageek_list_skills | read | List skills List the skills of the organisation with their ids. Rotageek API: GET /api/v1/skills. |
rotageek_list_payroll_codes | read | List payroll codes List the payroll codes that shifts and leave map to. Rotageek API: GET /api/v1/payrollcodes. |
rotageek_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. | |
rotageek_request_feature | Request a missing feature Tell usefulapi that the user needs something the Rotageek 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. | |
rotageek_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Rotageek (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+, $39/month or $390/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. | |
rotageek_cancel_subscription | Cancel the Pro subscription Cancel the caller's Rotageek 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 rotageek_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 user | $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 Rotageek server only. Subscribe with rotageek_upgrade (it returns a Stripe Checkout link). Cancel any time with rotageek_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running rotageek_upgrade before then undoes the cancel. Or write to [email protected].
See who is on shift at a site. Find open gaps in the rota. Review leave requests for a period. Book leave for a team member. Read a week's hours at a site. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Rotageek. The server calls the Rotageek API with your own Rotageek 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 Rotageek API username and Rotageek API user password. See Before you connect for where to find them.
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 Rotageek API username and Rotageek API user password. 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 Rotageek 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 Rotageek.
Yes, if you approve it. 1 of the 15 Rotageek tools can create or change data. The other 14 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 Rotageek server only. Cancel any time: Pro then runs to the end of the paid period. Run rotageek_usage_status to see how many calls you used.
Ask the AI to run rotageek_upgrade: it returns a Stripe Checkout link. To cancel, run rotageek_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 rotageek_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.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.