TidyCal integration
TidyCal is a scheduling and booking-page tool. Read the account, list and fetch bookings, cancel a booking, list booking types and their free time slots, book a time slot for someone (single or multi-session package bookings), create booking types (free or paid), list and add contacts, list Store orders, and manage teams: their bookings, booking types and members (invite or remove a user). Authentication is a personal access token created in TidyCal under Integrations, Advanced, Manage API keys (API access requires a paid plan), sent as a Bearer token in the Authorization header.
Say what should happen.
The workflow builds itself.
What you can do with TidyCal
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Booking, 4 operations
cancel_bookingCancel bookingPATCHCancels a booking by id, with an optional reason. Returns the cancelled booking (cancelled_at set).create_bookingCreate bookingPOSTBooks a booking type for a person (name, email, timezone) at starts_at (UTC), or several sessions through bookings for a package. Returns data as one booking, or a list for a package.get_bookingGet bookingGETReturns one booking by id: start and end time, timezone, contact, booking type, meeting URL, cancellation and payment details.list_bookingsList bookingsGETLists the account's bookings, 1 page at a time: filter by starts_at and ends_at dates, cancelled=true for cancelled ones only, include_teams=true to add team bookings.
Team user, 3 operations
add_team_userAdd team userPOSTInvites a user to a team by email (TidyCal sends the invitation email), with an optional role_name. Returns team_user_id.list_team_usersList team usersGETLists the members of a team: id, name and email of each.remove_team_userRemove team userDELETERemoves a member from a team by team user id.
Booking type, 2 operations
create_booking_typeCreate booking typePOSTCreates a booking type (a bookable meeting kind) on the account: title, description, duration_minutes and url_slug are required; price above 0 with payment_platform makes it paid.list_booking_typesList booking typesGETLists the account's booking types (the bookable meeting kinds): id, title, duration, URL slug, price and settings. Use an id with list_booking_type_timeslots or create_booking.
Contact, 2 operations
create_contactCreate contactPOSTAdds a contact to the account with a name, an email and an optional timezone. Returns the created contact.list_contactsList contactsGETLists the account's contacts (people who booked or were added): id, name, email, phone number and timezone.
Team, 2 operations
get_teamGet teamGETReturns one team by id: name and creation dates.list_teamsList teamsGETLists the teams the authenticated user has access to, with their ids and names.
Team booking type, 2 operations
create_team_booking_typeCreate team booking typePOSTCreates a booking type for a team: title, description, duration_minutes and url_slug are required; price above 0 with payment_platform makes it paid.list_team_booking_typesList team booking typesGETLists a team's booking types: id, title, duration, URL slug, price and settings.
Account, 1 operation
get_accountGet accountGETReturns the authenticated account: name, email, vanity path, language, profile picture URL, currency symbol and the date lifetime Pro was granted, if any.
Store order, 1 operation
list_store_ordersList store ordersGETLists Store sales and booking add-ons, newest completed first, 100 per page. status=completed returns only paid sales. Requires a paid plan.
Team booking, 1 operation
list_team_bookingsList team bookingsGETLists a team's bookings: filter by start_date and end_date, by the booker's email, by host_id, or by cancelled (true or false; leave out for all).
Timeslot, 1 operation
list_booking_type_timeslotsList booking type timeslotsGETLists the free time slots of a booking type between starts_at and ends_at (UTC), each with its start, end and seats left. Pass a slot's starts_at to create_booking.
Use TidyCal from Claude Code, Cursor or Codex
Connect TidyCal in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its TidyCal operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect TidyCal
- Create your workspace
Sign up free. Nothing to install.
- Connect TidyCal once
Add your TidyCal connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
TidyCal integration FAQ
What can you do with the TidyCal integration?
LiveContext exposes 19 operations on TidyCal, covering booking, team user, booking type and contact.
