hdls Scheduling

hdls Scheduling is a headless, MCP-native booking & scheduling backend. It manages availability, event types, and bookings, operated entirely through named tools your AI assistant calls. It stands in for tools like Calendly, Cal.com — same job, no UI to run.

💬 Just ask

"Find an open slot tomorrow afternoon and book a call with Acme."

You don't call these tools yourself — just tell your assistant in plain English. Everything below is the reference for when you (or your assistant) want the exact details.

How Scheduling is organized

The headline entity is the booking — start there, then attach the rest to it. Records connect by reference: an availability links to an event_type. The booking_event table is an append-only timeline — every change and note lands there and is never edited or deleted.

Entity	Purpose	Relates to
`booking`	A confirmed scheduled meeting between a host and invitee for an event type.	`event_type`
`event_type`	A bookable meeting template (duration, location, buffers) that invitees schedule against.	—
`availability`	A recurring weekly window (day_of_week + start/end time + timezone) when an event type is bookable.	`event_type`
`booking_event`	Append-only lifecycle log for a booking (created, rescheduled, cancelled, reminders, no_show).	`booking`

Common workflows

Each line is one real sequence of tool calls — your assistant chains them for you.

Set up a booking end to end: create_event_type → book_slot

Tools

Call these at https://hdls.ai/api/mcp/scheduling. Required fields you must supply; optional fields refine the call. You never pass tenant_id — it is stamped server-side.

Create

Tool	What it does	Required	Optional
`create_event_type`	Create a new event type.	`name`	`slug`, `description`, `host`, `duration_minutes`, `location_type`, `location_detail`

Update & advance

Tool	What it does	Required	Optional
`book_slot`	Book a slot.	`id`	—
`cancel_booking`	Cancel the booking.	`id`	—

Find & read

Tool	What it does	Required	Optional
`find_slots`	Find available slots.	—	`search`, `filters`, `limit`, `orderBy`
`list_bookings`	Search bookings by free-text and/or column filters (tenant-scoped, paginated).	—	`search`, `filters`, `limit`, `orderBy`

Field lists come from the product's live schema and are embedded in each tool's own description — read the tool description for the exact, current fields.

Field reference

Every field you can set on each record. Custom fields you add live alongside these in data.

`booking`

Field	Type	Required	Notes
`event_type_id`	id		Links to an `event_type`.
`title`	text	Yes	Display name.
`invitee_name`	text
`invitee_email`	text
`host`	text
`status`	text		Lifecycle state.
`starts_at`	timestamp	Yes
`ends_at`	timestamp	Yes
`timezone`	text
`location_detail`	text
`notes`	text
`data`	json		Free-form JSON — custom fields live here.

`event_type`

Field	Type	Required	Notes
`name`	text	Yes	Display name.
`slug`	text
`description`	text
`host`	text
`duration_minutes`	number
`location_type`	text
`location_detail`	text
`buffer_before`	number
`buffer_after`	number
`is_active`	true / false
`data`	json		Free-form JSON — custom fields live here.

`availability`

Field	Type	Required	Notes
`event_type_id`	id	Yes	Links to an `event_type`.
`day_of_week`	number	Yes
`start_time`	time	Yes
`end_time`	time	Yes
`timezone`	text
`is_active`	true / false
`data`	json		Free-form JSON — custom fields live here.

Tailor it with custom fields

Add fields without a schema change. add_custom_field defines one, list_custom_fields shows what's defined, and promote_custom_field (admin) shares a personal field with the whole workspace. The value lives in each row's data (JSON) and is set and read through the normal record tools. See Products, tools & custom fields for the full model.

Roles & safety

Tenant isolation is automatic. Your credential is pinned to one workspace; you never pass tenant_id, and you can only ever see your own data (enforced by Postgres row-level security).
Role-gated. Permissions run reader < member < admin < owner. Installing a product and promoting a custom field workspace-wide need admin/owner.
History is append-only. The booking_event timeline is never edited or deleted — it's your audit trail.

Connect

On the concierge (https://hdls.ai/api/mcp), run install_product({ slug: "scheduling" }) (admin/owner) to enable it for your workspace, then add https://hdls.ai/api/mcp/scheduling as a connector in your assistant — see Connect your assistant.

A worked example

The literal call your assistant makes when you ask it to create the headline record:

Tool: create_event_type
Arguments: {
  "name": "Acme Corp"
}

See All products · Connect your assistant · Automation