Rotase

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

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

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Rotase": {
      "url": "https://rotase.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (8)

• rotase_health read-only

  Read-only check that the Rotase scheduling service is available. Use this when connectivity or service availability is uncertain. It does not require a project and does not change data.

  Hints: read-only yes · destructive no · idempotent yes · open-world not declared

• rotase_examples read-only

  Read an example store, employees and complete project payload. Defaults to English labels; pass a supported language code to localize names. Call this when the project structure or field names are unknown. The returned project can be copied and edited before validation. This operation is read-only and does not access a user browser or saved project.

  Parameters:

  • language — string

  Hints: read-only yes · destructive no · idempotent yes · open-world not declared

• rotase_create_demo_project

  Create a localized demonstration project using the same project-creation operation as the Rotase API. The server chooses the current period in the requested timezone, loads the localized demo names and company name, applies the selected country calendar and can generate an initial schedule. The result is returned in the response; nothing is saved on the server or in a browser.

  Parameters:

  • kind — string
  • region — ['string', 'null'] — Optional region code supported by the selected country.
  • country — string — ISO country code, for example PL, DE, GB or US.
  • language — string — Demo language code, for example en, pl, de, fr or es.
  • timezone — string — IANA timezone, for example Europe/Warsaw.
  • closeOnHolidays — boolean

  Hints: read-only no · destructive no · idempotent no · open-world not declared

• rotase_validate_project read-only

  Validate a complete Rotase project payload without saving or modifying it. Use rotase_examples first if the payload shape is unknown. Call this before feasibility checks or schedule generation. The input is the project object itself, not a wrapper with an additional "project" property.

  Parameters:

  • project (required) — object
  • store (required) — object
  • employees (required) — array
  • schedules — array
  • preferences — array
  • availability — array
  • schemaVersion — string
  • monthlyTargets — array

  Hints: read-only yes · destructive no · idempotent yes · open-world not declared

• rotase_generate_schedule read-only

  Generate a monthly employee schedule from a complete Rotase project payload. Use rotase_examples to obtain a template, then rotase_validate_project first. The operation calculates and returns a schedule; it does not save a project, modify browser storage or create an account. Explain returned violations or shortages instead of assuming that every project is schedulable.

  Parameters:

  • project (required) — object
  • store (required) — object
  • employees (required) — array
  • schedules — array
  • preferences — array
  • availability — array
  • schemaVersion — string
  • monthlyTargets — array

  Hints: read-only yes · destructive no · idempotent yes · open-world not declared

• rotase_check_feasibility read-only

  Check whether a complete Rotase project can satisfy opening hours, staffing requirements, availability, rest rules and work-hour limits. Use after rotase_validate_project and before generation when the user asks whether a schedule is possible. This operation is read-only and does not save or modify the project.

  Parameters:

  • project (required) — object
  • store (required) — object
  • employees (required) — array
  • schedules — array
  • preferences — array
  • availability — array
  • schemaVersion — string
  • monthlyTargets — array

  Hints: read-only yes · destructive no · idempotent yes · open-world not declared

• rotase_schedule_report read-only

  Calculate per-store and per-employee statistics for a generated monthly schedule. Pass the complete project object and either provide the generated schedule as the top-level "schedule" property or put it in the project schedules array. This operation is read-only and does not save data.

  Parameters:

  • project (required) — object
  • store (required) — object
  • employees (required) — array
  • schedules — array
  • preferences — array
  • availability — array
  • schemaVersion — string
  • monthlyTargets — array

  Hints: read-only yes · destructive no · idempotent yes · open-world not declared

• rotase_export_csv read-only

  Export a generated monthly schedule as spreadsheet-compatible CSV. Pass the complete project object and either provide the generated schedule as the top-level "schedule" property or put it in the project schedules array. The response contains the CSV text; nothing is saved on the server.

  Parameters:

  • project (required) — object
  • store (required) — object
  • employees (required) — array
  • schedules — array
  • preferences — array
  • availability — array
  • schemaVersion — string
  • monthlyTargets — array

  Hints: read-only yes · destructive no · idempotent yes · open-world not declared

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.