Employee scheduling, staffing feasibility, localized demos, schedule reports and CSV export.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
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.
| Argument | Type | Description |
|---|---|---|
| store* | object | |
| project* | object | |
| employees* | array | |
| schedules | array | |
| preferences | array | |
| availability | array | |
| schemaVersion | string | |
| monthlyTargets | array |
{
"type": "object",
"required": [
"project",
"store",
"employees"
],
"properties": {
"store": {
"type": "object"
},
"project": {
"type": "object"
},
"employees": {
"type": "array",
"items": {
"type": "object"
}
},
"schedules": {
"type": "array",
"items": {
"type": "object"
}
},
"preferences": {
"type": "array"
},
"availability": {
"type": "array"
},
"schemaVersion": {
"type": "string"
},
"monthlyTargets": {
"type": "array"
}
},
"description": "The complete Rotase project object. Use the object returned as the \"project\" field by rotase_examples as a template. Required top-level sections are project, store and employees; availability, preferences, monthlyTargets and schedules may be empty arrays when unused.",
"additionalProperties": true
}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.
| Argument | Type | Description |
|---|---|---|
| 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 |
{
"type": "object",
"properties": {
"kind": {
"enum": [
"DEMO",
"EMPTY"
],
"type": "string"
},
"region": {
"type": [
"string",
"null"
],
"description": "Optional region code supported by the selected country."
},
"country": {
"type": "string",
"description": "ISO country code, for example PL, DE, GB or US."
},
"language": {
"type": "string",
"description": "Demo language code, for example en, pl, de, fr or es."
},
"timezone": {
"type": "string",
"description": "IANA timezone, for example Europe/Warsaw."
},
"closeOnHolidays": {
"type": "boolean"
}
},
"description": "Settings for the same projects/create API operation. All fields are optional; defaults are country PL, language en, kind DEMO and the timezone selected for the country.",
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| language | string |
{
"type": "object",
"properties": {
"language": {
"enum": [
"bg",
"cs",
"da",
"de",
"el",
"en",
"es",
"et",
"fi",
"fr",
"ga",
"hr",
"hu",
"it",
"lb",
"lt",
"lv",
"mt",
"nl",
"pl",
"pt",
"ro",
"sk",
"sl",
"sv",
"tr"
],
"type": "string"
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| store* | object | |
| project* | object | |
| employees* | array | |
| schedules | array | |
| preferences | array | |
| availability | array | |
| schemaVersion | string | |
| monthlyTargets | array |
{
"type": "object",
"required": [
"project",
"store",
"employees"
],
"properties": {
"store": {
"type": "object"
},
"project": {
"type": "object"
},
"employees": {
"type": "array",
"items": {
"type": "object"
}
},
"schedules": {
"type": "array",
"items": {
"type": "object"
}
},
"preferences": {
"type": "array"
},
"availability": {
"type": "array"
},
"schemaVersion": {
"type": "string"
},
"monthlyTargets": {
"type": "array"
}
},
"description": "The complete Rotase project object. Use the object returned as the \"project\" field by rotase_examples as a template. Required top-level sections are project, store and employees; availability, preferences, monthlyTargets and schedules may be empty arrays when unused.",
"additionalProperties": true
}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.
| Argument | Type | Description |
|---|---|---|
| store* | object | |
| project* | object | |
| employees* | array | |
| schedules | array | |
| preferences | array | |
| availability | array | |
| schemaVersion | string | |
| monthlyTargets | array |
{
"type": "object",
"required": [
"project",
"store",
"employees"
],
"properties": {
"store": {
"type": "object"
},
"project": {
"type": "object"
},
"employees": {
"type": "array",
"items": {
"type": "object"
}
},
"schedules": {
"type": "array",
"items": {
"type": "object"
}
},
"preferences": {
"type": "array"
},
"availability": {
"type": "array"
},
"schemaVersion": {
"type": "string"
},
"monthlyTargets": {
"type": "array"
}
},
"description": "The complete Rotase project object. Use the object returned as the \"project\" field by rotase_examples as a template. Required top-level sections are project, store and employees; availability, preferences, monthlyTargets and schedules may be empty arrays when unused.",
"additionalProperties": true
}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.
No arguments.
{
"type": "object",
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| store* | object | |
| project* | object | |
| employees* | array | |
| schedules | array | |
| preferences | array | |
| availability | array | |
| schemaVersion | string | |
| monthlyTargets | array |
{
"type": "object",
"required": [
"project",
"store",
"employees"
],
"properties": {
"store": {
"type": "object"
},
"project": {
"type": "object"
},
"employees": {
"type": "array",
"items": {
"type": "object"
}
},
"schedules": {
"type": "array",
"items": {
"type": "object"
}
},
"preferences": {
"type": "array"
},
"availability": {
"type": "array"
},
"schemaVersion": {
"type": "string"
},
"monthlyTargets": {
"type": "array"
}
},
"description": "The complete Rotase project object. Use the object returned as the \"project\" field by rotase_examples as a template. Required top-level sections are project, store and employees; availability, preferences, monthlyTargets and schedules may be empty arrays when unused.",
"additionalProperties": true
}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.
| Argument | Type | Description |
|---|---|---|
| store* | object | |
| project* | object | |
| employees* | array | |
| schedules | array | |
| preferences | array | |
| availability | array | |
| schemaVersion | string | |
| monthlyTargets | array |
{
"type": "object",
"required": [
"project",
"store",
"employees"
],
"properties": {
"store": {
"type": "object"
},
"project": {
"type": "object"
},
"employees": {
"type": "array",
"items": {
"type": "object"
}
},
"schedules": {
"type": "array",
"items": {
"type": "object"
}
},
"preferences": {
"type": "array"
},
"availability": {
"type": "array"
},
"schemaVersion": {
"type": "string"
},
"monthlyTargets": {
"type": "array"
}
},
"description": "The complete Rotase project object. Use the object returned as the \"project\" field by rotase_examples as a template. Required top-level sections are project, store and employees; availability, preferences, monthlyTargets and schedules may be empty arrays when unused.",
"additionalProperties": true
}