They are meant to be used in order — read the calendar's open slots, then book one of them — so the assistant offers times that are genuinely free rather than proposing one that has already gone. Everything is scoped to a booking calendar you name, and the key travels with each request from your client.
A server over the OnceHub scheduling API with two tools: read the open time slots on a booking calendar, and book one of them for a named guest. The vendor runs a hosted endpoint, and the repository builds the same server if you would rather run it yourself.
- The open slots on a booking calendar, optionally narrowed to a date range
- A booked meeting carrying the guest's name, email and time zone
- Meeting mode chosen per booking — a video provider, an address already on file, or the guest's phone
- Custom intake fields passed through onto the booking when the calendar asks for them
- A confirmation with the booking identifier, so the assistant can say it is done and mean it
A OnceHub API key, sent as a bearer token by your client rather than stored on the server, plus the identifier of the booking calendar you want to work against. This is a remote HTTP server, not a local stdio one, so the client has to support remote MCP servers; self-hosting it needs Python, and a Docker image is included.
One command plus a key — npx -y mcp-remote https://mcp.oncehub.com/sse, then supply credentials