get_staff_next_holiday returns the day the person is actually back at work, not the day after the holiday ends — working times, shifts, public holidays and other absences all sit in between. That is exactly the kind of question a model guessing from a calendar gets confidently wrong.
An analytics layer over freispace, the scheduling system for media and post-production teams. Lookups are name-based — partial names match — and every answer is scoped to what the calling user is allowed to see.
- Who and what — get_current_user resolves 'me' to a staff record, get_staffs lists the team, find_resources searches rooms, equipment and staff in one call
- Availability — get_availability returns free slots and fully-free days for staff, suites, resources or a site over a window of up to 92 days, and says whether a required duration fits
- Your own day — get_my_schedule, get_my_tasks, get_open_tasks
- People — get_staff_projects, get_staff_collaborators, get_staff_next_holiday, get_staff_holiday_quota
- Projects — get_project_stats with the project's timespan, get_project_team, get_project_tasks
- Commercials — get_invoices, get_offers, and get_orders with their connected offers and invoices inline
- search_docs answers questions about how freispace itself works
The npm package @freispace/mcp-server-analytics over stdio. It needs a freispace Flagship account and an MCP API key — during the beta that key comes from freispace support. Permissions are enforced per user, so the model only reaches data that user could already open.
One command — npx -y @freispace/mcp-server-analytics