
Official MCP RegistryListed
Shift Scheduler
Builds optimal 24/7 staff rosters with a real MILP solver: rest rules, skills, nights, fairness.
First seen 2 Oct 2026. Evidence as of 16 Nov 2026.
5
Tools
From an anonymous probe
1
Source listings
Each with its own history
5
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| build_shift_roster | Solve a staff rostering problem to optimality with a MILP solver and return who works which shift each day, coverage, unfilled posts, hours per person and warnings. Solves take 5-60 s. Pass either `example` (to solve a built-in example as-is) or the roster input fields. If the result has status 'running', call get_shift_roster_result with its job_id. If it has status 'too_large', shorten the horizon or reduce people/shift types and retry. If it has status 'busy', wait the retry_after_seconds it gives and call again -- one call at a time, never in parallel. Safe defaults (e.g. the next 7 days when `days` is omitted) are listed in the result's `assumptions`; tell the user about them. Roster input. Minimal example: {"days": ["2026-10-05", "2026-10-06"], "shifts": [{"shift": "Day", "start": "07:00", "end": "19:00"}, {"shift": "Night", "start": "19:00", "end": "07:00", "night": "yes"}], "demands": [{"name": "RN", "penalty": 500}], "people": [{"name": "Ana", "cost": 40, "max_hw": 48}, ...], "grids": {"RN": {"2026-10-05|Day": 2, "2026-10-05|Night": 1}}, "parameters": {"MinRestHours": 11}}. Call get_shift_example for complete, realistic inputs. | Read-only |
| check_request | Describe what the user wants in plain words and get back whether this server can do it, which limits it would hit, and the closest thing it CAN do. Instant, no solve. Use it when unsure the tool fits (shift swaps, payroll, time clocks, very large teams or long horizons). | Read-only |
| get_shift_example | Return the full input JSON of one example, in exactly the shape build_shift_roster accepts. Edit it (names, days, headcounts, rules) to match the user's situation. | Read-only |
| get_shift_roster_result | Fetch the result of a build_shift_roster job that returned status 'running'. Waits up to wait_seconds; call again while status is 'running'. Jobs expire 15 minutes after they finish. | Read-only |
| list_shift_examples | List the built-in example rostering problems (hospital ward, 3-shift plant, security post, fire station, 24/7 help desk). Use one as a starting point for the user's own roster. | Read-only |
Change history
- build_shift_roster: input schema changed
- check_request: tool added
- build_shift_roster: input schema changed (+goal)
- build_shift_roster: description changed (+"If it has status 'busy', wait the retry_after_seconds it gives and call again -- one call at a time, never in parallel. Safe defaults (e.g. the next 7 days when `days` is omitted) are listed in the result's `assumptions`; tell the user about them.")
- server instructions changed (+"If unsure the tool fits, call check_request first. Send ONE build_shift_roster call at a time, never several in parallel: the solver runs one roster at a time and parallel calls just queue or get 'busy'.")
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | com.kindoflost.staff-scheduling/shift-scheduler | 2 Oct 2026 | 16 Nov 2026 | 1 |