mcpbeat Sign in

Rotawise Shift Scheduler MCP Server

answering

Rotawise Shift Scheduler is answering right now. Last checked 11 min ago. It exposes 2 tools.

Weekly staff shift schedules

Uptime history 67 hours of history
67 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
371 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Rotawise Shift Scheduler every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add shift-scheduler --transport http https://shift-scheduler.zovo.one/mcp
Settings → Connectors → Add custom connector, then paste this address
https://shift-scheduler.zovo.one/mcp
~/.codex/config.toml
[mcp_servers.shift-scheduler]
url = "https://shift-scheduler.zovo.one/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "shift-scheduler": {
      "url": "https://shift-scheduler.zovo.one/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "shift-scheduler": {
      "type": "http",
      "url": "https://shift-scheduler.zovo.one/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

generate
generate_shift_schedule
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).
schedule
check_schedule
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.

Endpoints

URLTransportStateLatencyChecked
https://shift-scheduler.zovo.one/mcp streamable-http answering 401 ms 11 min ago

Alternatives to Rotawise Shift Scheduler

same job, measured the same way
Shift Scheduler
by kindoflost-staff-scheduling

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

5 tools answering
Shiftyasan Shift Scheduling
by shiftyasan

Generate optimized work shift schedules from staffing demand, availability and fairness rules.

19 installs/wk answering
Tvmaze MCP
by mrfentmen

TVMaze show search and schedules.

16 installs/wk local only
Shiftly Staff Scheduling Demo
by zhiyong-easyshiftplan

No-login MCP demo for isolated fictional staff schedules; drafts are never saved or published.

5 tools answering
Dooit
by dooit

Read and run a user's task board: tasks, schedules, projects, and weekly/monthly/yearly goals.

answering
Nflverse
by pipeworx-io

nflverse — NFL play-by-play, player and team stats, schedules and injury

46 tools answering
Amortiza Loan Planner
by theluckystrike

Mortgage & loan schedules

2 tools answering
Rotase
by rotase

Employee scheduling, staffing feasibility, localized demos, schedule reports and CSV export.

8 tools answering

Rotawise Shift Scheduler — questions

Answers built from our own checks of this server.

What can Rotawise Shift Scheduler do?
It exposes 2 tools, read directly from the server on our last check. Among them: check_schedule, generate_shift_schedule. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Rotawise Shift Scheduler working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 371 ms. The bar chart above shows every period we have measured.
How do I connect Rotawise Shift Scheduler?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Rotawise Shift Scheduler need an API key?
No. Rotawise Shift Scheduler completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Rotawise Shift Scheduler?
It answers our handshake in 371 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.