Planerio MCP by usefulapi

Read shifts, staffing requirements, staff, employees, absences and vacation days in Planerio.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
95%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,687Tokens (tool definitions)
~2.0 KBTypical response size
Moderate attention impact (1.32% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "planerio": {
      "url": "https://planerio.usefulapi.io/mcp"
    }
  }
}

Remote endpoints

https://planerio.usefulapi.io/mcpstreamable-http

What it can do

Tool inventory

Tools (6)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢planerio_list_shifts(start_date, end_date, updated_after, include_drafts, include_deleted, ...)

List the planned shifts between two dates: shift id, start and end time, employee (name, personnel number, employee_uuid), shift group, workplace, location, tags and last change. By default only published plans and no deleted shifts. Use updated_after for changes since a date. Sorted by start time. Read-only. Long lists are cut: use offset to continue.

Input Schema

{
  "type": "object",
  "properties": {
    "start_date": {
      "type": "string",
      "pattern": "^20\\d{2}-\\d{2}-\\d{2}$",
      "description": "First day, YYYY-MM-DD."
    },
    "end_date": {
      "type": "string",
      "pattern": "^20\\d{2}-\\d{2}-\\d{2}$",
      "description": "Last day, YYYY-MM-DD."
    },
    "updated_after": {
      "description": "Only shifts changed after this date.",
      "type": "string",
      "pattern": "^20\\d{2}-\\d{2}-\\d{2}$"
    },
    "include_drafts": {
      "description": "Also shifts from plans in draft status.",
      "type": "boolean"
    },
    "include_deleted": {
      "description": "Also deleted shifts (with shift_deleted_at).",
      "type": "boolean"
    },
    "include_comments": {
      "description": "Add the free-text shift comments. Slower and larger.",
      "type": "boolean"
    },
    "limit": {
      "description": "Rows to return, default 100, maximum 1000.",
      "type": "integer",
      "minimum": 1,
      "maximum": 1000
    },
    "offset": {
      "description": "Rows to skip (use next_offset of a truncated reply).",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "required": [
    "start_date",
    "end_date"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢planerio_list_shift_cards(start_date, end_date, limit, offset)

List the staffing requirement defined in shift cards: workplace, location, shift group, validity, weekdays, times, shift type, required qualifications and the shifts of each card with priority and pre-planned employee. Filter by validity dates. Read-only.

Input Schema

{
  "type": "object",
  "properties": {
    "start_date": {
      "description": "Leave out cards that ended before this date.",
      "type": "string",
      "pattern": "^20\\d{2}-\\d{2}-\\d{2}$"
    },
    "end_date": {
      "description": "Leave out cards that start after this date.",
      "type": "string",
      "pattern": "^20\\d{2}-\\d{2}-\\d{2}$"
    },
    "limit": {
      "description": "Rows to return, default 100, maximum 1000.",
      "type": "integer",
      "minimum": 1,
      "maximum": 1000
    },
    "offset": {
      "description": "Rows to skip (use next_offset of a truncated reply).",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢planerio_list_staff(limit, offset)

List the current staff supply for resource planning: name, personnel number, primary shift group, qualifications, weekly hours and days, hours per weekday, entry and exit date. Use it together with planerio_list_shift_cards. For plain employee master data use planerio_list_employees. Read-only.

Input Schema

{
  "type": "object",
  "properties": {
    "limit": {
      "description": "Rows to return, default 100, maximum 1000.",
      "type": "integer",
      "minimum": 1,
      "maximum": 1000
    },
    "offset": {
      "description": "Rows to skip (use next_offset of a truncated reply).",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢planerio_list_employees(reference_date, limit, offset)

List the employee master data valid on a reference date: employee_uuid, names, email, personnel number, shift groups, entry and exit date, work schedule (weekly hours, job title, tariff), supervisor, cost center, occupational category, date of birth. Personal data: ask only for what the task needs. Read-only.

Input Schema

{
  "type": "object",
  "properties": {
    "reference_date": {
      "description": "Day for which the data is valid, YYYY-MM-DD. Default: today.",
      "type": "string",
      "pattern": "^20\\d{2}-\\d{2}-\\d{2}$"
    },
    "limit": {
      "description": "Rows to return, default 100, maximum 1000.",
      "type": "integer",
      "minimum": 1,
      "maximum": 1000
    },
    "offset": {
      "description": "Rows to skip (use next_offset of a truncated reply).",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢planerio_list_absences(start_date, end_date, include_open, include_rejected, include_deleted, ...)

List the absence periods that overlap two dates: employee, dates and times, calendar and working days, status (ACCEPTED, OPEN, REJECTED, DELETED), absence type and comment. By default only approved absences. Use include_open for requests that wait for approval. Read-only. Long lists are cut: use offset to continue.

Input Schema

{
  "type": "object",
  "properties": {
    "start_date": {
      "type": "string",
      "pattern": "^20\\d{2}-\\d{2}-\\d{2}$",
      "description": "First day, YYYY-MM-DD."
    },
    "end_date": {
      "type": "string",
      "pattern": "^20\\d{2}-\\d{2}-\\d{2}$",
      "description": "Last day, YYYY-MM-DD."
    },
    "include_open": {
      "description": "Also absences that wait for approval.",
      "type": "boolean"
    },
    "include_rejected": {
      "description": "Also rejected absences.",
      "type": "boolean"
    },
    "include_deleted": {
      "description": "Also deleted absences.",
      "type": "boolean"
    },
    "include_recurring": {
      "description": "Also single dates of recurring absences.",
      "type": "boolean"
    },
    "include_days": {
      "description": "One row per calendar day with cost_in_days, cost_in_hours and day_segment. Changes the reply shape.",
      "type": "boolean"
    },
    "updated_after": {
      "description": "Only absences changed after this date.",
      "type": "string",
      "pattern": "^20\\d{2}-\\d{2}-\\d{2}$"
    },
    "limit": {
      "description": "Rows to return, default 100, maximum 1000.",
      "type": "integer",
      "minimum": 1,
      "maximum": 1000
    },
    "offset": {
      "description": "Rows to skip (use next_offset of a truncated reply).",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "required": [
    "start_date",
    "end_date"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢planerio_get_vacation_days(date, limit, offset)

Get the vacation days per employee for one year: allowance, carry-over from the last year, expired, requested, approved, taken and remaining. Only for Planerio 1.5 (not 2.0); Planerio replaces this endpoint in 2026/27. Read-only.

Input Schema

{
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^20\\d{2}-\\d{2}-\\d{2}$",
      "description": "A day in the year to calculate, for example 2026-01-01. Days taken count up to this day."
    },
    "limit": {
      "description": "Rows to return, default 100, maximum 1000.",
      "type": "integer",
      "minimum": 1,
      "maximum": 1000
    },
    "offset": {
      "description": "Rows to skip (use next_offset of a truncated reply).",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "required": [
    "date"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded6 tools