MCP Server

planner

com.vigotime/planner
Business & Operations Public & reachable MCP 2025-11-25

What this MCP does

Submits and monitors rule-based workforce duty-roster optimization jobs using employees, shifts, availability, preferences, and labor-planning constraints.

account_balance
Aktuelles Token-Guthaben der eigenen Organisation (Solves kosten Tokens).
Input schema
{'type': 'object', 'title': 'account_balanceArguments', 'properties': {}}
Output schema
{'type': 'object', 'title': 'account_balanceDictOutput', 'additionalProperties': True}
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).
Input schema
{'type': 'object', 'title': 'example_payloadArguments', 'properties': {'kind': {'type': 'string', 'title': 'Kind', 'default': 'simple'}}}
Output schema
{'type': 'object', 'title': 'example_payloadDictOutput', 'additionalProperties': True}
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.
Input schema
{'type': 'object', 'title': 'service_infoArguments', 'properties': {}}
Output schema
{'type': 'object', 'title': 'service_infoDictOutput', 'additionalProperties': True}
solve_result
Ergebnis eines fertigen Solve-Jobs: assignments [{employee_id, shift_id, date}], unassigned_shifts mit Begründung, Statistiken.
Input schema
{'type': 'object', 'title': 'solve_resultArguments', 'required': ['job_id'], 'properties': {'job_id': {'type': 'string', 'title': 'Job Id'}}}
Output schema
{'type': 'object', 'title': 'solve_resultDictOutput', 'additionalProperties': True}
solve_status
Status eines Solve-Jobs (pending/running/completed/failed) inkl. Fortschritt.
Input schema
{'type': 'object', 'title': 'solve_statusArguments', 'required': ['job_id'], 'properties': {'job_id': {'type': 'string', 'title': 'Job Id'}}}
Output schema
{'type': 'object', 'title': 'solve_statusDictOutput', 'additionalProperties': True}
solve_submit
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}.
Input schema
{'type': 'object', 'title': 'solve_submitArguments', 'required': ['payload'], 'properties': {'payload': {'type': 'object', 'title': 'Payload', 'additionalProperties': True}}}
Output schema
{'type': 'object', 'title': 'solve_submitDictOutput', 'additionalProperties': True}
Added
example_payload
Sept. 17, 2026, 12:38 p.m.
Added
service_info
Sept. 17, 2026, 12:38 p.m.
Added
account_balance
Sept. 17, 2026, 12:38 p.m.
Added
solve_result
Sept. 17, 2026, 12:38 p.m.
Added
solve_status
Sept. 17, 2026, 12:38 p.m.
Added
solve_submit
Sept. 17, 2026, 12:38 p.m.