Skip to content

Rotawise Shift Scheduler

by theluckystrike · remote · no sign-in to list tools · v1.0.1 · published by GitHub user theluckystrike

Weekly staff shift schedules

Changes · 2
CompareRegistry entry

2 tools: 2 change things.

Scanned Oct 22, 2026

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

claude mcp add --transport http shift-scheduler https://shift-scheduler.zovo.one/mcp

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • Warngenerate_shift_schedule

    The server marks "generate_shift_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_shift_schedule" says "generate": a word for a change.

    What this check looks for
  • Warncheck_schedule

    The server marks "check_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_schedule" says "schedule": a word for a change.

    What this check looks for

Tools

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

2 tools

Changes things 2Claude Code: ask
  • check_scheduleUse this when the user already has a work schedule and wants it checked against scheduling rules: "check this schedule", "does anyone have a clopening", "is anyone over 40 hours", …1 finding

    Why it is in this group

    • The name "check_schedule" says "schedule": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "check_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_schedule" says "schedule": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Use this when the user already has a work schedule and wants it checked against scheduling rules: "check this schedule", "does anyone have a clopening", "is anyone over 40 hours", "fix this schedule, Sam cannot work Mondays". Takes the shifts with the people on them (typed, or an attached schedule CSV/XLSX grid or list) plus optional staff rules (roles, max hours, unavailable days) and reports each problem it finds: overlapping or double-booked shifts, less rest than the rule between shifts, too many shifts per day or days in a row, over max hours or overtime, wrong role, unavailable times, and shifts below headcount. Returns hours per person and a PDF, Excel and per-employee calendar files of the checked schedule. Does not change the schedule itself (generate_shift_schedule builds a corrected one) and does not give legal advice on scheduling laws.

    Annotations the server declares

    • title: Check a shift schedule
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • generate_shift_scheduleUse this when the user wants an employee schedule maker or work schedule maker: build a weekly staff or shift schedule for a restaurant, cafe, retail store, clinic front desk or si…1 finding

    Why it is in this group

    • The name "generate_shift_schedule" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "generate_shift_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_shift_schedule" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Use this when the user wants an employee schedule maker or work schedule maker: build a weekly staff or shift schedule for a restaurant, cafe, retail store, clinic front desk or similar from staff names, roles or skills, availability (days or times people cannot work), min/max hours, and the shifts to cover with headcount, e.g. "make a weekly schedule for 6 employees", "need 2 people on each shift, nobody over 40 hours", "make a rotating schedule so weekends are fair", "who should close on friday", "Sam cannot work Mondays". Accepts typed lists or an attached availability CSV/XLSX. A deterministic solver checks each hard rule (roles, availability, max hours, overtime cap, minimum rest between shifts, shifts per day, consecutive days), balances weekend and closing shifts, and when coverage is impossible returns each open shift with the binding reason. Returns hours per person, overtime flags, fairness ranges, and a printable PDF, Excel file and per-employee calendar (.ics) files. Overnight shifts and daylight-saving weeks are counted in real elapsed hours. Does not post schedules, message staff, track clock-ins or run payroll. Do not use for job searches or for checking a schedule the user already made (use check_schedule).

    Annotations the server declares

    • title: Make a shift schedule
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true

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.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http shift-scheduler https://shift-scheduler.zovo.one/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": [],
    "ask": [
      "mcp__shift-scheduler__generate_shift_schedule",
      "mcp__shift-scheduler__check_schedule"
    ],
    "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.