Skip to content

Shift Scheduler

by staff-scheduling.kindoflost.com · remote · no sign-in to list tools · v1.0.0 · published by com.kindoflost.staff-scheduling

Builds optimal 24/7 staff rosters with a real MILP solver: rest rules, skills, nights, fairness.

Changes · 1
CompareRegistry entry

4 tools: 1 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http shift-scheduler https://staff-scheduling.kindoflost.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 1Claude Code: ask
  • build_shift_rosterSolve 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. 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.

    Annotations the server declares

    • title: Build an optimized shift roster
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Claude Code: allow
  • get_shift_exampleReturn the full input JSON of one example, in exactly the shape build_shift_roster accepts.No findings

    Why it is in this group

    • The name "get_shift_example" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get an example roster input
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_shift_roster_resultFetch the result of a build_shift_roster job that returned status 'running'.No findings

    Why it is in this group

    • The name "get_shift_roster_result" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a roster result
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_shift_examplesList the built-in example rostering problems (hospital ward, 3-shift plant, security post, fire station, 24/7 help desk).No findings

    Why it is in this group

    • The name "list_shift_examples" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List example rosters
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http shift-scheduler https://staff-scheduling.kindoflost.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__shift-scheduler__list_shift_examples",
      "mcp__shift-scheduler__get_shift_example",
      "mcp__shift-scheduler__get_shift_roster_result"
    ],
    "ask": [
      "mcp__shift-scheduler__build_shift_roster"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as shift-scheduler. Review it before you use it.