A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Rotase is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Employee scheduling, staffing feasibility, localized demos, schedule reports and CSV export.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http rotase-mcp https://rotase.com/mcp
# 2 — ask your agent for something these tools do
# rotase_health, rotase_examples, rotase_create_demo_project and 5 more
Rotase costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ROAll 1 server
rotase1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http rotase-mcp https://rotase.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | no | ISO country code, for example PL, DE, GB or US. |
| region | string/null | no | Optional region code supported by the selected country. |
| language | string | no | Demo language code, for example en, pl, de, fr or es. |
| timezone | string | no | IANA timezone, for example Europe/Warsaw. |
| kind | string | no | — |
| closeOnHolidays | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schemaVersion | string | no | — |
| project | object | yes | — |
| store | object | yes | — |
| employees | array | yes | — |
| availability | array | no | — |
| preferences | array | no | — |
| monthlyTargets | array | no | — |
| schedules | array | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schemaVersion | string | no | — |
| project | object | yes | — |
| store | object | yes | — |
| employees | array | yes | — |
| availability | array | no | — |
| preferences | array | no | — |
| monthlyTargets | array | no | — |
| schedules | array | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schemaVersion | string | no | — |
| project | object | yes | — |
| store | object | yes | — |
| employees | array | yes | — |
| availability | array | no | — |
| preferences | array | no | — |
| monthlyTargets | array | no | — |
| schedules | array | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schemaVersion | string | no | — |
| project | object | yes | — |
| store | object | yes | — |
| employees | array | yes | — |
| availability | array | no | — |
| preferences | array | no | — |
| monthlyTargets | array | no | — |
| schedules | array | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schemaVersion | string | no | — |
| project | object | yes | — |
| store | object | yes | — |
| employees | array | yes | — |
| availability | array | no | — |
| preferences | array | no | — |
| monthlyTargets | array | no | — |
| schedules | array | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Rotase or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Rotase can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.