Skedda API and MCP server Let your AI agent run your Skedda bookings.

ToolWhat it doesAccess

• list_spaces Spaces of the venue with type, tags and capacity. read

  Lists the venue spaces as the scheduler shows them, with name, type, tags and capacity. Filter by tag, type or minimum capacity. Nothing is changed.

  MCP callskedda_read → list_spaces

  REST endpointGET https://cotlet.dev/api/v1/skedda/spaces

  Parameters

  Parameters: list_spaces

  Name	Type	Description
  space_tag string	string	Only spaces with this space tag.
  space_type string	string	Only spaces of this type, as named in the venue.
  min_capacity integer	integer	Only spaces that seat at least this many people.

  Example response

  {
    "spaces": [
      {
        "space_id": "spc_101",
        "name": "Studio A",
        "type": "Rehearsal room",
        "tags": [
          "Music"
        ],
        "capacity": 8
      },
      {
        "space_id": "spc_102",
        "name": "Studio B",
        "type": "Rehearsal room",
        "tags": [
          "Music"
        ],
        "capacity": 4
      }
    ]
  }

• list_bookings Bookings in a date range with space, holder, type, price and payment status. read

  Returns the bookings of the List view for the dates you give, oldest first. Each row has the space or spaces, holder, title, type, price and payment status. Filter by space, holder, booking type or a search term in the title, space names and custom fields. Nothing is changed.

  MCP callskedda_read → list_bookings

  REST endpointGET https://cotlet.dev/api/v1/skedda/bookings

  Parameters

  Parameters: list_bookings

  Name	Type	Description
  date_from date required	date	First day to list.
  date_to date required	date	Last day to list.
  space_id string	string	Only bookings in this space, from list_spaces.
  holder_email string	string	Only bookings held by this user.
  booking_type string	string	user, internal or unavailable.
  search string	string	Text to find in the title, space names or custom fields.

  Example input

  {
    "date_from": "2026-10-01",
    "date_to": "2026-10-01"
  }

  Example response

  {
    "bookings": [
      {
        "booking_id": "bkg_2041",
        "title": "Band rehearsal",
        "type": "User",
        "spaces": [
          "Studio A"
        ],
        "holder": "Jake Miller",
        "start": "2026-11-02T18:00:00+01:00",
        "end": "2026-11-02T21:00:00+01:00",
        "price": 45,
        "payment_status": "Unpaid"
      },
      {
        "booking_id": "bkg_2042",
        "title": "Podcast recording",
        "type": "User",
        "spaces": [
          "Studio B"
        ],
        "holder": "Priya Shah",
        "start": "2026-11-03T10:00:00+01:00",
        "end": "2026-11-03T11:30:00+01:00",
        "price": 30,
        "payment_status": "Paid"
      }
    ]
  }

• get_booking One booking with holder, notes, price, custom fields and repeat rule. read

  Returns the full record of one booking: spaces, times, title, notes, holder, price, payment status, custom fields and the repeat sequence when there is one. Admin-only custom fields are included, so treat the result as private. Nothing is changed.

  MCP callskedda_read → get_booking

  REST endpointGET https://cotlet.dev/api/v1/skedda/bookings/{booking_id}

  Parameters

  Parameters: get_booking

  Name	Type	Description
  booking_id string required	string	Booking ID from list_bookings.

  Example input

  {
    "booking_id": "booking_8c41d2"
  }

  Example response

  {
    "booking_id": "bkg_2041",
    "title": "Band rehearsal",
    "type": "User",
    "spaces": [
      "Studio A"
    ],
    "holder": {
      "name": "Jake Miller",
      "email": "jake@example.com"
    },
    "start": "2026-11-02T18:00:00+01:00",
    "end": "2026-11-02T21:00:00+01:00",
    "notes": "Bringing own amp",
    "price": 45,
    "payment_status": "Unpaid",
    "custom_fields": [
      {
        "name": "Equipment",
        "value": "Drum kit"
      }
    ],
    "repeat": null
  }

• create_booking Book one or more spaces for a user, the venue or as unavailable. writeasks first

  Fills the New booking form as a system user. Booking type user needs a holder, internal and unavailable bookings have none, and unavailable blocks the space. Conflicts are never allowed, so a taken time is refused. Repeat rules from the form are supported. A user holder may be emailed, depending on the venue notification settings. By default you confirm each call; you can switch that off for this tool.

  MCP callskedda_write → create_booking

  REST endpointPOST https://cotlet.dev/api/v1/skedda/bookings

  Parameters

  Parameters: create_booking

  Name	Type	Description
  space_ids string[] required	string[]	Spaces to book, IDs from list_spaces.
  start datetime required	datetime	Start in the venue time zone.
  end datetime required	datetime	End in the venue time zone.
  booking_type string	string	user, internal or unavailable. Default: user.
  holder_email string	string	Holder of a user booking. Leave out to book for yourself.
  title string	string	Booking title.
  repeat object	object	Repeat rule: { frequency: day | week | month | year, until: date }.

  Example input

  {
    "space_ids": [
      "spc_101",
      "spc_102"
    ],
    "start": "2026-12-24T00:00:00+01:00",
    "end": "2026-12-26T23:59:00+01:00",
    "booking_type": "unavailable",
    "title": "Closed for holidays"
  }

  Example response

  {
    "booking_id": "bkg_2050",
    "title": "Closed for holidays",
    "type": "Unavailable",
    "spaces": [
      "Studio A",
      "Studio B"
    ],
    "start": "2026-12-24T00:00:00+01:00",
    "end": "2026-12-26T23:59:00+01:00",
    "occurrences": 1
  }

• update_booking Change the time, spaces, title, holder or price of a booking. writeasks first

  Edits a booking as the edit screen does: date and time, spaces, title, notes, holder and price. Only the fields you send change. For a repeat booking, scope picks one occurrence, this and following, or the full series. Changing a single occurrence separates it from the series. The holder may be told about important changes. By default you confirm each call; you can switch that off for this tool.

  MCP callskedda_write → update_booking

  REST endpointPATCH https://cotlet.dev/api/v1/skedda/bookings/{booking_id}

  Parameters

  Parameters: update_booking

  Name	Type	Description
  booking_id string required	string	Booking ID from list_bookings.
  space_ids string[]	string[]	New spaces, IDs from list_spaces.
  start datetime	datetime	New start.
  end datetime	datetime	New end.
  title string	string	New title.
  holder_email string	string	New holder of a user booking.
  price number	number	New price.
  scope string	string	For a repeat booking: single (this occurrence), following (this and following) or series (the full series). Default: single.

  Example input

  {
    "booking_id": "booking_8c41d2"
  }

  Example response

  {
    "booking_id": "bkg_2041",
    "spaces": [
      "Studio B"
    ],
    "start": "2026-11-02T18:00:00+01:00",
    "end": "2026-11-02T21:00:00+01:00",
    "updated": true
  }

• cancel_booking Remove a booking from the schedule. writeasks first

  Removes a booking as the Cancel action does. A booking with payment status Paid cannot be removed until its payment status is changed. For a repeat booking, scope picks one occurrence, this and following, or the full series. The holder may be notified. By default you confirm each call; you can switch that off for this tool.

  MCP callskedda_write → cancel_booking

  REST endpointPOST https://cotlet.dev/api/v1/skedda/bookings/{booking_id}/cancel

  Parameters

  Parameters: cancel_booking

  Name	Type	Description
  booking_id string required	string	Booking ID from list_bookings.
  scope string	string	For a repeat booking: single (this occurrence), following (this and following) or series (the full series). Default: single.

  Example input

  {
    "booking_id": "booking_8c41d2"
  }

  Example response

  {
    "booking_id": "bkg_2042",
    "status": "cancelled",
    "scope": "single"
  }

ToolWhat it doesAccess

• list_booking_requests Pending booking requests waiting for an admin. read

  Lists the requests on the Booking requests page that wait for approval, oldest first, with requester, space, time and title. Booking approvals exist only on the Premier plan, so a venue without them returns an error. Requests do not appear on the scheduler and do not block each other. Nothing is changed.

  MCP callskedda_read → list_booking_requests

  REST endpointGET https://cotlet.dev/api/v1/skedda/booking-requests

  Parameters

  Parameters: list_booking_requests

  Name	Type	Description
  space_id string	string	Only requests for this space.

  Example response

  {
    "requests": [
      {
        "request_id": "req_310",
        "title": "Choir practice",
        "space": "Studio A",
        "requester": "Ana Lopez",
        "start": "2026-11-05T19:00:00+01:00",
        "end": "2026-11-05T21:00:00+01:00",
        "submitted": "2026-10-30T09:12:00+01:00"
      }
    ]
  }

• approve_booking_request Approve a pending request and create the booking. writeasks first

  Approves a request from the Booking requests page, which creates the booking with the requested details. The requester is emailed, and if the booking involves payment they are charged only after approval. Quotas and rules were checked when the request was submitted. By default you confirm each call; you can switch that off for this tool.

  MCP callskedda_write → approve_booking_request

  REST endpointPOST https://cotlet.dev/api/v1/skedda/requests/{request_id}/booking-request/approve

  Parameters

  Parameters: approve_booking_request

  Name	Type	Description
  request_id string required	string	Request ID from list_booking_requests.

  Example input

  {
    "request_id": "request_8c41d2"
  }

  Example response

  {
    "request_id": "req_310",
    "status": "approved",
    "booking_id": "bkg_2051"
  }

• reject_booking_request Reject a pending request with an optional note. writeasks first

  Rejects a request from the Booking requests page. The optional note is sent to the requester with the rejection email, and no booking is created. By default you confirm each call; you can switch that off for this tool.

  MCP callskedda_write → reject_booking_request

  REST endpointPOST https://cotlet.dev/api/v1/skedda/requests/{request_id}/booking-request/reject

  Parameters

  Parameters: reject_booking_request

  Name	Type	Description
  request_id string required	string	Request ID from list_booking_requests.
  note string	string	Rejection note for the requester.

  Example input

  {
    "request_id": "request_8c41d2"
  }

  Example response

  {
    "request_id": "req_311",
    "status": "rejected"
  }

ToolWhat it doesAccess

• get_usage_summary Booking count, hours of usage and total price for a period. read

  Returns the totals the List view shows to system users: total booking matches, total usage in hours and minutes, and total price when the venue uses pricing. A two-hour booking of two spaces counts as four hours, and unavailable bookings are left out of usage. Nothing is changed.

  MCP callskedda_read → get_usage_summary

  REST endpointGET https://cotlet.dev/api/v1/skedda/usage-summary

  Parameters

  Parameters: get_usage_summary

  Name	Type	Description
  date_from date required	date	First day of the period.
  date_to date required	date	Last day of the period.
  holder_email string	string	Only bookings held by this user.
  booking_type string	string	user, internal or unavailable.

  Example input

  {
    "date_from": "2026-10-01",
    "date_to": "2026-10-01"
  }

  Example response

  {
    "period": {
      "from": "2026-10-26",
      "to": "2026-11-01"
    },
    "bookings": 18,
    "usage": "31 h 30 min",
    "total_price": 940
  }

• get_activity_feed Log of new, updated, cancelled, charged and checked-in bookings. read

  Reads the booking activity feed from the List view, newest first, with a timestamp, who did it and which booking. Filter by time range, activity type or a search term. Only system users can open the feed. Nothing is changed.

  MCP callskedda_read → get_activity_feed

  REST endpointGET https://cotlet.dev/api/v1/skedda/activity-feed

  Parameters

  Parameters: get_activity_feed

  Name	Type	Description
  date_from date required	date	First day of the log.
  date_to date required	date	Last day of the log.
  activity_type string	string	new, update, cancel, charge or check-in.
  search string	string	Text to find in the log.

  Example input

  {
    "date_from": "2026-10-01",
    "date_to": "2026-10-01"
  }

  Example response

  {
    "events": [
      {
        "time": "2026-11-02T08:40:00+01:00",
        "activity": "update",
        "booking_id": "bkg_2042",
        "title": "Podcast recording",
        "by": "Maya Brooks"
      },
      {
        "time": "2026-11-01T16:05:00+01:00",
        "activity": "new",
        "booking_id": "bkg_2041",
        "title": "Band rehearsal",
        "by": "Jake Miller"
      }
    ]
  }

• list_users Venue users with email, user tags and system tag. read

  Lists the people on the Users page with name, email, user tags and system tag. Filter by a search term or a tag. It returns personal details, so use it only for the job at hand. Nothing is changed.

  MCP callskedda_read → list_users

  REST endpointGET https://cotlet.dev/api/v1/skedda/users

  Parameters

  Parameters: list_users

  Name	Type	Description
  search string	string	Part of a name or email.
  tag string	string	Only users with this user tag.

  Example response

  {
    "users": [
      {
        "name": "Jake Miller",
        "email": "jake@example.com",
        "tags": [
          "Band"
        ],
        "system_tag": null
      },
      {
        "name": "Maya Brooks",
        "email": "maya@example.com",
        "tags": [],
        "system_tag": "System Admin"
      }
    ]
  }