ResDiary API and MCP server Let your AI agent run the diary with you.

ToolWhat it doesAccess

• list_bookings Read the bookings in your diary for one date, with party size, status and notes. read

  Returns the bookings the diary shows for that date in time order, each with booking_id, reference, visit time, party size, status, guest name, customer_id and the booking note. Walk-ins appear without a customer_id. A Bumped booking is one a staff member still has to put back on a table. It changes nothing.

  MCP callresdiary_read → list_bookings

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

  Parameters

  Parameters: list_bookings

  Name	Type	Description
  date string required	string	Visit date in YYYY-MM-DD.
  status string	string	Booking status to keep, for example Booked, Confirmed, Unconfirmed, Cancelled or Bumped. Defaults to all.
  limit integer	integer	How many bookings to return.

  Example input

  {
    "date": "date"
  }

  Example response

  {
    "date": "2026-10-31",
    "bookings": [
      {
        "booking_id": "bk_21041",
        "reference": "BHCQ66D",
        "time": "18:30",
        "party_size": 2,
        "status": "Confirmed",
        "guest": "Alex Rivera",
        "customer_id": "cu_8812",
        "booking_note": "Anniversary"
      },
      {
        "booking_id": "bk_21047",
        "reference": "BHCQ70M",
        "time": "19:15",
        "party_size": 4,
        "status": "Unconfirmed",
        "guest": "Sam Lee",
        "customer_id": "cu_9120",
        "booking_note": "Deposit due"
      },
      {
        "booking_id": "bk_21052",
        "reference": "BHCQ74T",
        "time": "20:00",
        "party_size": 6,
        "status": "Confirmed",
        "guest": "Harper Lane",
        "customer_id": "cu_7304",
        "booking_note": ""
      }
    ]
  }

• get_booking Read one booking with its guest, notes and reminders. read

  Returns the booking as the diary shows it: visit date and time, party size, status, booking note, internal reminders with their due dates, and the guest with customer_id. Contact details are left out of the response. It changes nothing.

  MCP callresdiary_read → get_booking

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

  Parameters

  Parameters: get_booking

  Name	Type	Description
  booking_id string required	string	A booking_id from list_bookings.

  Example input

  {
    "booking_id": "booking_8c41d2"
  }

  Example response

  {
    "booking_id": "bk_21047",
    "reference": "BHCQ70M",
    "date": "2026-10-31",
    "time": "19:15",
    "party_size": 4,
    "status": "Unconfirmed",
    "booking_note": "Deposit due",
    "reminders": [
      {
        "text": "Collect deposit",
        "due": "2026-10-30"
      }
    ],
    "guest": {
      "customer_id": "cu_9120",
      "name": "Sam Lee"
    }
  }

• list_available_times List the open times in your diary for a date and party size. read

  Returns the times your venue would offer for that party size on that date, as its online booking shows them, with the service name where there is one. It holds no table: a time can be gone by the time you book. Your own limits, such as maximum online covers, still apply.

  MCP callresdiary_read → list_available_times

  REST endpointGET https://cotlet.dev/api/v1/resdiary/available-times

  Parameters

  Parameters: list_available_times

  Name	Type	Description
  date string required	string	Visit date in YYYY-MM-DD.
  party_size integer required	integer	Number of guests.
  time string	string	Time in HH:MM to search around. Defaults to 19:00.

  Example input

  {
    "date": "date",
    "party_size": 1
  }

  Example response

  {
    "date": "2026-11-07",
    "party_size": 4,
    "times": [
      {
        "time": "19:30",
        "service": "Dinner"
      },
      {
        "time": "20:00",
        "service": "Dinner"
      },
      {
        "time": "20:15",
        "service": "Dinner"
      }
    ]
  }

• list_waitlist Read the parties on your W8LIST for a date. read

  Returns each waiting party with its booking_id, guest name, party size, the time it asked for and its W8LIST status, in the order your diary shows them. It reads the queue only: it does not text anyone. It changes nothing.

  MCP callresdiary_read → list_waitlist

  REST endpointGET https://cotlet.dev/api/v1/resdiary/waitlists

  Parameters

  Parameters: list_waitlist

  Name	Type	Description
  date string required	string	Date in YYYY-MM-DD.

  Example input

  {
    "date": "date"
  }

  Example response

  {
    "date": "2026-10-31",
    "waitlist": [
      {
        "booking_id": "bk_21090",
        "guest": "Jordan Park",
        "party_size": 2,
        "requested_time": "19:00",
        "status": "Queued"
      },
      {
        "booking_id": "bk_21093",
        "guest": "Taylor Green",
        "party_size": 5,
        "requested_time": "19:30",
        "status": "Queued"
      }
    ]
  }

ToolWhat it doesAccess

• create_booking Add a booking to your diary for a guest. writeasks first

  Adds the booking to the diary the way the Book button does, so the call waits for your approval. ResDiary sends the guest a confirmation email, and a booking that needs a deposit or a stored card stays Unconfirmed until the guest completes it. Returns the booking_id and the reference. By default you confirm each call; you can switch that off for this tool.

  MCP callresdiary_write → create_booking

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

  Parameters

  Parameters: create_booking

  Name	Type	Description
  date string required	string	Visit date in YYYY-MM-DD.
  time string required	string	A time from list_available_times, HH:MM.
  party_size integer required	integer	Number of guests.
  customer_id string	string	An existing profile from search_customers. Leave out for a new guest.
  first_name string	string	Guest first name, for a new guest.
  last_name string	string	Guest last name, for a new guest.
  mobile string	string	Guest mobile number, for a new guest.
  booking_note string	string	A note on the booking, for example "high chair" or "birthday".

  Example input

  {
    "date": "2026-11-07",
    "time": "20:00",
    "party_size": 4,
    "first_name": "Chidi",
    "last_name": "Okafor",
    "mobile": "+447700900123",
    "booking_note": "Birthday dinner"
  }

  Example response

  {
    "booking_id": "bk_21107",
    "reference": "BHCQ81K",
    "date": "2026-11-07",
    "time": "20:00",
    "party_size": 4,
    "status": "Confirmed",
    "guest": "Chidi Okafor"
  }

• update_booking Change the time, party size or booking note of a booking. writeasks first

  Edits the booking in the diary and the guest sees the change, so the call waits for your approval. A new time must come from list_available_times for the new party size. When the change does not fit, the booking stays as it was and the call returns why. By default you confirm each call; you can switch that off for this tool.

  MCP callresdiary_write → update_booking

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

  Parameters

  Parameters: update_booking

  Name	Type	Description
  booking_id string required	string	A booking_id from list_bookings.
  time string	string	A new time from list_available_times, HH:MM. Leave out to keep the time.
  party_size integer	integer	New number of guests.
  booking_note string	string	New booking note.

  Example input

  {
    "booking_id": "booking_8c41d2"
  }

  Example response

  {
    "booking_id": "bk_21052",
    "reference": "BHCQ74T",
    "date": "2026-10-31",
    "time": "19:45",
    "party_size": 6,
    "status": "Confirmed"
  }

• cancel_booking Cancel a booking in your diary. writeasks first

  Sets the booking to Cancelled and frees the table, so the call waits for your approval. A cancelled booking cannot be restored by a tool; create a new booking instead. A deposit already paid is handled in ResDiary, not by this call. By default you confirm each call; you can switch that off for this tool.

  MCP callresdiary_write → cancel_booking

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

  Parameters

  Parameters: cancel_booking

  Name	Type	Description
  booking_id string required	string	A booking_id from list_bookings.

  Example input

  {
    "booking_id": "booking_8c41d2"
  }

  Example response

  {
    "booking_id": "bk_21047",
    "reference": "BHCQ70M",
    "status": "Cancelled"
  }

ToolWhat it doesAccess

• search_customers Find guest profiles in your customer database by name, email or mobile number. read

  Returns matching profiles with customer_id, name, customer type and the date of the last visit, best match first. Email and mobile number are left out of the response; you search by them but do not read them back. It changes nothing.

  MCP callresdiary_read → search_customers

  REST endpointGET https://cotlet.dev/api/v1/resdiary/customers/search

  Parameters

  Parameters: search_customers

  Name	Type	Description
  query string required	string	Part of a name, an email address or a mobile number.
  limit integer	integer	How many profiles to return.

  Example input

  {
    "query": "query"
  }

  Example response

  {
    "customers": [
      {
        "customer_id": "cu_7304",
        "name": "Harper Lane",
        "customer_type": "Regular",
        "last_visit": "2026-10-17"
      },
      {
        "customer_id": "cu_7311",
        "name": "Harper Lowe",
        "customer_type": "",
        "last_visit": "2026-06-02"
      }
    ]
  }

• get_customer Read one guest profile: customer type, customer notes and booking history. read

  Returns the guest's name, customer type, customer notes (the ones that show every time this guest books), the number of past visits and the last visits with date, party size and status. A profile has one customer type. Contact details are left out of the response.

  MCP callresdiary_read → get_customer

  REST endpointGET https://cotlet.dev/api/v1/resdiary/customers/{customer_id}

  Parameters

  Parameters: get_customer

  Name	Type	Description
  customer_id string required	string	A customer_id from list_bookings or search_customers.

  Example input

  {
    "customer_id": "customer_8c41d2"
  }

  Example response

  {
    "customer_id": "cu_7304",
    "name": "Harper Lane",
    "customer_type": "Regular",
    "notes": [
      "Prefers the window table"
    ],
    "visits": 11,
    "last_visits": [
      {
        "date": "2026-10-17",
        "party_size": 4,
        "status": "Closed"
      },
      {
        "date": "2026-09-05",
        "party_size": 2,
        "status": "Closed"
      }
    ]
  }

• add_customer_note Add a customer note to a guest profile. write

  Adds a customer note, the kind that shows every time this guest books. Notes are for your staff, the guest is not told, and you remove the note on the profile in one step, so it runs without asking you. Returns the profile's notes after the change.

  MCP callresdiary_write → add_customer_note

  REST endpointPOST https://cotlet.dev/api/v1/resdiary/customers/{customer_id}/note

  Parameters

  Parameters: add_customer_note

  Name	Type	Description
  customer_id string required	string	A customer_id from list_bookings or search_customers.
  note string required	string	Note text, for example "Shellfish allergy" or "Prefers a quiet table".

  Example input

  {
    "customer_id": "customer_8c41d2",
    "note": "note"
  }

  Example response

  {
    "customer_id": "cu_9120",
    "name": "Sam Lee",
    "notes": [
      "Shellfish allergy"
    ]
  }

• set_customer_type Set the customer type of a guest profile. write

  Sets the profile's customer type, the tag your team sees every time that profile books and that you can segment marketing by. A profile has one customer type, so this replaces the old one; set the old name back to undo it. It only uses types that exist in your venue's list, and nobody outside your team sees it, so it runs without asking you.

  MCP callresdiary_write → set_customer_type

  REST endpointPUT https://cotlet.dev/api/v1/resdiary/customers/{customer_id}/type

  Parameters

  Parameters: set_customer_type

  Name	Type	Description
  customer_id string required	string	A customer_id from search_customers.
  customer_type string required	string	A customer type your venue already has under Settings > Customer Types, for example "Regular".

  Example input

  {
    "customer_id": "customer_8c41d2",
    "customer_type": "customer type"
  }

  Example response

  {
    "customer_id": "cu_7311",
    "name": "Harper Lowe",
    "customer_type": "Regular",
    "previous": ""
  }

• add_booking_reminder Add an internal reminder to a booking. write

  Adds a reminder that only your staff see; it appears in the diary on the due date. The guest is not told, and you delete the reminder on the booking in one step, so it runs without asking you. Returns the reminders on the booking after the change.

  MCP callresdiary_write → add_booking_reminder

  REST endpointPOST https://cotlet.dev/api/v1/resdiary/bookings/{booking_id}/reminder

  Parameters

  Parameters: add_booking_reminder

  Name	Type	Description
  booking_id string required	string	A booking_id from list_bookings.
  text string required	string	What staff should do, for example "Collect deposit".
  due_date string required	string	Due date in YYYY-MM-DD.

  Example input

  {
    "booking_id": "booking_8c41d2",
    "text": "text",
    "due_date": "due date"
  }

  Example response

  {
    "booking_id": "bk_21047",
    "reminders": [
      {
        "text": "Collect deposit",
        "due": "2026-10-30"
      }
    ]
  }