Zooza MCP Server
MCP server for Zooza — class scheduling, attendance, and booking for activity businesses.
| Endpoint | https://mcp.zooza.app/mcp (streamable-http) |
|---|---|
| Registry version | 0.2.0 |
| Now | 18 tools · grade F (40) · pin ts_1e4b43ca8a26db9eed43389646f4c7c2 · protocol 2025-06-18 |
| First / last listed | 2026-10-28 02:16 UTC / 2026-10-28 02:16 UTC |
| Grade over time | 2026-10-28: F (40), 18 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: get_terminology whoami classes_find_courses classes_find_resource classes_find_classes bookings_find sessions_find_events sessions_get_attendance sessions_mark_attendance classes_update sessions_update sessions_cancel bookings_copy_booking comms_send_message reports_get_data get_skill get_tool_schema call_tool
get_terminology | Search the Zooza domain glossary. Returns canonical term names, definitions, cross-language synonyms, disambiguation rules, and AI guidance notes. No Zooza API call is made — purely local lookup against the compiled glossary. Use this to resolve ambiguous user input before calling operational tools. Examples: query="hodina" → Session; query="kurz", language="sk" → Programme; category="product-hier params: query, language, category |
whoami | Returns the connected user's identity, the companies they can operate on, regional context, and the session's token state. Call ONCE at the start of every conversation.
How to interpret the response:
- 'status: "ok"' — authenticated, at least one company available. Pick a 'company_id' from 'companies' for follow-up calls (ask the user if more than one exists).
- 'status: "no_companies"' — authen params: none |
classes_find_courses | Search the company's courses by name (substring match) and optionally by registration_type. Returns a slim list of matches — `{id, name, registration_type, target_audience, price, schedules_count, ...}` — enough to disambiguate, not enough to act. Use this whenever the user names a course in natural language; never demand a raw course_id. Archived courses are excluded by default (pass `include_arc params: company_id, name, registration_type, include_archived, page, page_size |
classes_find_resource | Resolve a NAME the operator said into an id, for four kinds of company-level records. Pick `kind`:
- `place` — venues. Returns `{id, name, city, street, rooms: [{id, name, capacity}]}`. Rooms are inlined because picking a venue is usually followed by picking a room. Filters: name, city.
- `billing_period` — term blocks (e.g. "Autumn 2026"). Returns `{id, name, active, period_start, period_end}`; params: company_id, kind*, name, city, place_id, course_id, include_inactive, page, page_size |
classes_find_classes | Search this company's CLASSES — the scheduled groups inside a programme (a "class" / "group" / "skupina"; internally a *schedule*) — by name (substring) and resolve them to a `schedule_id`. Reach for this whenever the user names a specific group rather than a whole programme ("the Nejaké class", "the Monday 5pm group", "her Wednesday ballet class"), or whenever a downstream tool needs a `schedule_ params: company_id, name, course_id, trainer_id, place_id, billing_period_id, day, registration_type, in_trial, active_only, lead_only, with_sessions, sort, include_archived, page, page_size |
bookings_find | Find this company's bookings — a client's enrolment in a class (registration; "prihláška"/"Buchung") — and resolve them to a `registration_id`, or a client to a `user_id`. Use for "is X enrolled?", "who's in this class?", "who hasn't paid?" (set `payment_status:["unpaid","partially_paid"]`), and "find client X". Filter by `search` (loose: name/email/phone) or `name`, by `course_id`/`schedule_id` ( params: company_id, search, name, course_id, schedule_id, billing_period_id, place_id, user_id, registration_id, status, payment_status, distinct, inactive_only, include_extra_fields, created_from, created_to, page, page_size |
sessions_find_events | List **events** (scheduled sessions of classes) in the caller's company. Use this whenever you need to resolve an `event_id` from natural language ("my next class," "Monday's ballet," "all swim sessions this week," "Sarah's classes tomorrow") before chaining into another tool like `sessions_get_attendance` or `sessions_mark_attendance`. With no filters at all, returns the company's **upcoming** sc params: company_id, ids, from, to, date, status, type, schedule_id, course_id, trainer_id, place_id, room_id, segment_id, billing_period_id, sort, page, page_size |
sessions_get_attendance | Read who's enrolled in **one event** (a single session of a class) and their current attendance, so you can show the list and then mark it. Pass an `event_id`; the tool returns each enrolled attendee, their current attendance value (if already marked), and per-row context the LLM needs to mark attendance correctly: `allowed_statuses[]` (the statuses the **current caller** is permitted to set for T params: company_id, event_id* |
sessions_mark_attendance | Record per-attendee attendance for **one event** (a single session of a class — e.g. "Monday Ballet on 2026-06-03 at 09:00"). Pass an `event_id` and a list of attendees, each with their own attendance value (`attended`, `noshow`, `canceled`, `going`, `ignore`). Each value is set on **that one attendee for that one event**, never on the event as a whole. The tool writes each attendee individually a params: company_id, event_id*, attendees* |
classes_update | Edit one or more existing classes (a "class"/"timetable" is the recurring group within a programme) — name, price, registration fee, capacity, make-up/replacement extra capacity ("počet miest navyše pre náhradné hodiny" → extra_capacity/extra_capacity_usage, NOT registrations_cap, which caps the NUMBER OF REGISTRATIONS), registration-count cap, billing period, online-registration, trial lessons, s params: company_id, token, confirmed, schedule_ids, changes, session_scope, confirm_course_change |
sessions_update | Edit specific individual sessions (events) of a class, OR add new sessions to a class. Two modes, one tool.
NOT for a change that holds from a date onward or for every session ("from next week Jana teaches the Monday class", "the class moves to Room B") — that is ONE classes_update call with session_scope ('upcoming' or 'all'), never a per-session edit of each date.
EDIT-MODE — pass `event_ids` params: company_id, token, confirmed, event_ids, changes, schedule_id, sessions, notify |
sessions_cancel | Cancel one or more scheduled SESSIONS of a class so they do not take place — "cancel Tuesday's sessions", "the pool is closed on Friday", "Martina is ill all week, cancel her classes". A cancelled session stays visible in Zooza with a cancelled status; it is NOT deleted.
Scope the call to exactly ONE entity: `event_ids`, a single `date`, a single `trainer_id` with `from`/`to`, a single `schedule_ params: company_id, token, confirmed, event_ids, date, trainer_id, schedule_id, place_id, from, to, reason, public_reason, notify, include_past, replacement_date, replacement_place_id, replacement_room_id |
bookings_copy_booking | Copy or move a client's existing booking into a different class. COPY creates a second booking and leaves the original in place — use it when the client is continuing into a new term or adding a class alongside their current one. MOVE relocates the booking itself, carrying its payment history and debt, and the client is no longer in the old class — use it when they are switching.
TWO CALLS. First params: company_id, token, confirmed, registration_id, target_schedule_id, action, payments, status, start, target_event_id, send_confirmation |
comms_send_message | Email clients of this company. Describe the audience (a course/programme, a class schedule, a specific booking, one client, a saved segment, an ad-hoc cohort, or course-level labels) and the content (an existing template `type` from comms_list_templates, or a custom subject + body which may use *|MERGE_VAR|* tags from comms_list_merge_vars).
TWO CALLS. First WITHOUT `token`: sends NOTHING. Return params: company_id, token, confirmed, confirm_large_send, channel, audience, content, marketing, schedule_at, bcc |
reports_get_data | Return the REAL, pre-aggregated numbers for ONE business question about an activity brand — and the basis for SHOWING it. This is how you show an operator a report / dashboard / chart of their business numbers (occupancy, unpaid, churn, attendance, trials, retention, revenue, "how are we doing", per programme / venue / instructor): call this, then COMPOSE a focused report as an ARTIFACT in the con params: view, from, to, company_id |
get_skill | Returns the full markdown playbook for one of the registered skills. Call this BEFORE starting a flow named in the server's instructions — the playbook contains the interview steps, mapping rules, and confirmation pattern for that scenario. Available skills: business-model-validator, class-management, communication, feedback-nudge, negotiate-terminology, report-compose, report-discovery, report-pa params: name* |
get_tool_schema | Returns the description and exact input schema of a Zooza tool, including tools not in your tool list (call_tool lists them). Call it once per tool before that tool's first call_tool. params: name* |
call_tool | Runs a Zooza tool by name. Use it for every Zooza tool that is NOT in your tool list — these exist and work; never send the user to another app because a Zooza tool isn't listed. Call get_tool_schema(name) first for the arguments. Write tools behave exactly as when called directly: the first call previews and returns a token, the second (token + confirmed:true) applies.
Tools reachable this way:
- params: name*, arguments |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.