Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 132 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Code & DevOps
Read staff, locations, shifts, gaps and leave; create leave requests in Rotageek.
0 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Outdated check
Last connection measurement is over 24 hours old. Current availability is unknown.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 4 | 0 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Rotageek MCP by usefulapi
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http rotageek-mcp-by-usefulapi https://rotageek.usefulapi.io/mcpCapabilities
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}.
DiscoveredGet one location by id, with its settings. Rotageek API: GET /api/v1/locations/{locationId}.
DiscoveredGet 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}.
DiscoveredGet one user by id: name, contact details, primary location and status. Rotageek API: GET /api/v1/users/{userId}.
DiscoveredList the open gaps (unfilled shifts) for one or more locations between two date-times. Rotageek API: GET /api/v1/gaps/locations.
DiscoveredList the leave requests of the organisation, optionally in a leave year or date range. Rotageek API: GET /api/v1/leave/requests.
DiscoveredList the leave types (for example holiday or sickness) and their ids. Rotageek API: GET /api/v1/leave/types.
DiscoveredList 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}.
DiscoveredList the users assigned to one location. Rotageek API: GET /api/v1/locations/{locationId}/users.
DiscoveredList the locations (sites) of the organisation. Rotageek API: GET /api/v1/locations.
DiscoveredList the payroll codes that shifts and leave map to. Rotageek API: GET /api/v1/payrollcodes.
DiscoveredList the job positions (roles) of the organisation with their ids. Rotageek API: GET /api/v1/positions.
DiscoveredList the skills of the organisation with their ids. Rotageek API: GET /api/v1/skills.
DiscoveredList 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}.
DiscoveredList 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.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 54 ms | 15 |