Remote vigotime Planner server that lets an assistant submit duty-roster solve jobs, track their progress, and retrieve the resulting shift assignments.
What you can do
Submit a self-contained roster solve request with dates, department, employees, shifts and optional planning rules, then poll the job status and progress and fetch the finished result with assignments, unassigned shifts and statistics, plus reasons for gaps. Check the organization's remaining token balance and read the running service's build version, commit and build time for support. Generate ready-to-run example payloads for simple, wishes-based or ArbZG rule-based scenarios.
When to use it
Useful when you want an assistant to build or adjust staff duty rosters under rules such as rest periods and maximum consecutive days, or to check whether a solve finished and what it produced. Also handy for support requests that need the current service build.
Requirements
A remote endpoint at api.vigotime.com over streamable HTTP; the description mentions an API key or OAuth, though the manifest declares no authentication, environment variables or headers. Solves consume tokens from the organization's balance, so an account with credit is needed.
Before you install
Solves cost tokens from the organization's balance, so submitting jobs spends credit. Solve requests contain employee and shift data that is sent to the remote service. Jobs are submitted and run remotely, and results should be checked against the unassigned shifts and their reasons before being used.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.vigotime%2Fplanner/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Reicht einen Dienstplan-Solve-Job ein. `payload` ist der self-contained Request: Pflicht: start_date, end_date (ISO), department {id}, employees [{id, contractHoursPerWeek, qualificationIds}], shifts [{id, departmentId, name, startTime, endTime, shiftType, minStaff}]. Optional u. a.: planning_rules, wishes, vacations, sick_leaves, holiday_dates, locked_assignments, social_points, wish_costs, config {timeout_seconds}. vacations darf Termine NACH end_date enthalten — noetig bei Datums-Kopplungsregeln mit Block-Tagen hinter dem Fenster (siehe Instructions). Datenschutz: IDs statt Namen verwenden. Antwort: {job_id, status}.
Parameterspayloadrequired
solve_status
Status eines Solve-Jobs (pending/running/completed/failed) inkl. Fortschritt.
Parametersjob_idrequired
solve_result
Ergebnis eines fertigen Solve-Jobs: assignments [{employee_id, shift_id, date}], unassigned_shifts mit Begründung, Statistiken.
Parametersjob_idrequired
account_balance
Aktuelles Token-Guthaben der eigenen Organisation (Solves kosten Tokens).
Takes no parameters.
service_info
Build-Stand des laufenden Planner-Service: version (fortlaufende Build-Nummer), gitCommit, buildTime (UTC). Fuer Support-Anfragen und um Ergebnisse einem Software-Stand zuzuordnen.
Takes no parameters.
example_payload
Ein sofort lauffähiger Beispiel-Payload für solve_submit. kind='simple' (1 Woche, 3 MA, 2 Schichten), kind='wishes' (Wünsche, Social Points, Wunschkosten) oder kind='rules' (ArbZG-Planungsregeln: 11 h Ruhe hart + max. 5 Folgetage — zeigt, wie Regeln den Plan formen; Param-Namen sind exakt, falsche werden still ignoriert).
Parameterskind
Version history
1
v1.0.0LatestSep 16, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
