SuperSaaS Slots

SuperSaaS slots MCP server

A read-only MCP server that reports which slots are free on a public SuperSaaS schedule. It covers intraday appointments, date-only schedules such as nightly rentals, and capacity schedules with seats per class. Give it a SuperSaaS schedule URL, or a business page that links to one, such as https://www.down-the-hatch.nl/reserveren/. No account or API key is needed.

Not the official SuperSaaS MCP server. SuperSaaS offers its own server at https://www.supersaas.com/mcp, which authenticates as your account — via OAuth or a per-account bearer token — and can read and change anything the account can: bookings, users, prices, credit balances. Use that one when the goal is managing your own schedules with an AI assistant. This package answers a different question: what is available on someone else's public schedule, or on your own as a visitor sees it, without credentials and without touching anything. It reads only pages an anonymous browser can already load, never books, and has no account of any kind. Pick by which side of the counter you are on: SuperSaaS's server is the merchant's till, this one is the window display.

Licensed under the MIT License. How the schedule data is read is documented in INTERNALS.md.

Install

After publication, use Python 3.10+:

pip install supersaas-slots-mcp

For local development from the project directory:

python3 -m venv .venv.venv/bin/python -m pip install -e .

Dependencies are declared in pyproject.toml; FastMCP is pinned to version 4.0.10. Both supersaas-slots and supersaas-slots-mcp start the server.

Connect

Configure a stdio MCP server in your MCP client:

{  "mcpServers": {    "supersaas-slots": {      "command": "/absolute/path/to/supersaas-mcp/.venv/bin/supersaas-slots"    }  }}

Replace the command path with the absolute path to your project directory. The client must allow this local process to make HTTPS requests to www.supersaas.nl, www.supersaas.com and www.supersaas.co.uk.

Or run it from PyPI with uvx:

{  "mcpServers": {    "supersaas-slots": {      "command": "uvx",      "args": ["supersaas-slots-mcp"]    }  }}

Tool

find_available_slots

{  "schedule_url": "https://www.supersaas.nl/schedule/downthehatch/SLEEP",  "from_date": "2026-10-19",  "through_date": "2026-10-25"}

schedule_url may be a business page instead. The server scans it for a link to a SuperSaaS schedule, follows it, and reports the origin as linked_from. If the HTML names none — single-page sites keep the link in a bundled script — it also scans the page's own JS files, limited to the same origin and to the first ten scripts.

Response

{  "schedule_url": "https://www.supersaas.nl/schedule/downthehatch/SLEEP",  "from_date": "2026-10-19",  "through_date": "2026-10-25",  "time_basis": "schedule wall time; epoch values interpreted as UTC",  "unit": "slot",  "duration_minutes": 180,  "count": 1,  "truncated": false,  "slots": [{ "start": "2026-10-22 09:30", "end": "2026-10-22 12:30" }]}

Times are schedule wall-clock strings, YYYY-MM-DD HH:MM. truncated describes slots only, so compare it against count before treating a list as complete. Data is re-fetched on every call, so results change as other people book.

unit is slot, night, or class. Appointment schedules return slot with duration_minutes set to the appointment length. Date-only schedules such as rentals return night and add three fields:

{  "unit": "night",  "duration_minutes": 1440,  "check_in": "14:00",  "check_out": "12:00",  "slots": [{ "start": "2026-10-05 14:00", "end": "2026-10-06 12:00" }],  "stays": [{ "start": "2026-10-05", "end": "2026-10-10", "nights": 5 }]}

Each slots entry is one night, from check-in on a date to check-out on the next; duration_minutes is the nominal 1440-minute night. stays merges consecutive free nights into the ranges you can actually book, so four adjacent nights become one four-night stay. Use slots when pricing per night and stays when offering a date range to the customer.

Capacity schedules, such as Jazzercise, return unit: "class" and one entry per class with an ordinary seat available:

{  "unit": "class",  "slots": [{    "id": 101,    "start": "2026-10-01 19:00",    "end": "2026-10-01 20:00",    "title": "CardioSculpt",    "location": "Village Hall",    "capacity": 40,    "booked": 32,    "waiting": 0,    "available": 8  }]}

The class id is SuperSaaS's slot ID. A class with unlimited capacity has null for capacity and available. SuperSaaS includes waiting-list places in booked, so available is capacity - booked + waiting. Classes without an ordinary seat are excluded, even when the schedule offers a waiting list. Class lengths can vary, so there is no top-level duration_minutes in this mode.

Errors

Every error names a cause, and most have a remedy:

Scope

Supported: public resource schedules with a single resource, fixed appointment duration, weekly opening hours with per-day exceptions and blocked ranges, booked appointments, buffer time, advance-booking limits, and both slot and night units. Public capacity schedules list classes with available seats, including each class's title, location, capacity, booked and waiting counts, and remaining seats.

SuperSaaS offers three schedule types; service schedules are reported as unsupported. Also not modeled: recurring rules, per-user limits, minimum-stay rules, and payment-dependent availability. An available slot is a calculated candidate, not a booking guarantee — the booking page remains authoritative at reservation time.

Development

.venv/bin/python -m unittest -v test_supersaas_mcp.py.venv/bin/python check_release.py

The tests run offline against saved copies of three real resource schedules and a Jazzercise capacity response, so they do not drift as customers book. See INTERNALS.md for what each fixture pins.

Release

Releases use PyPI Trusted Publishing and MCP Registry GitHub OIDC. Before the first release:

1. Create a pypi environment in this GitHub repository and allow deployment from version tags. In PyPI, register a pending trusted publisher for owner RichieB2B, repository supersaas-slots-mcp, workflow release.yml, and environment pypi. The PyPI project does not need to exist yet.
2. Create an mcp-registry GitHub environment and allow deployment from version tags. The Registry uses GitHub OIDC, so it needs no registry token.
3. Keep the version in pyproject.toml, server.json (both version fields), and the FastMCP server constructor in sync. check_release.py verifies this and accepts the candidate tag with --tag v0.3.1. Commit the release before tagging it.
4. Push a matching tag, for example git tag v0.3.1 && git push origin v0.3.1.

The release workflow tests and builds the distribution, publishes it to PyPI, then submits server.json to the MCP Registry. The CI workflow runs tests and package checks on pushes and pull requests. A pushed release tag publishes externally; review its commit and environment settings first.