Skip to content
MCP server

resOS MCP by usefulapi

Read bookings, guests and availability; create, update or cancel bookings in resOS.

Install
Runs
Remotely
Version
1.6.0
Listing updated
4 days ago

About resOS MCP by usefulapi

resOS MCP by usefulapi is an MCP server. It runs as a hosted remote server, so there is nothing to install locally.

Install

Run in a terminal

claude mcp add --transport http resos https://resos.usefulapi.io/mcp

Add to Settings → Connectors → Add custom connector

https://resos.usefulapi.io/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "resos": {
      "url": "https://resos.usefulapi.io/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "resos": {
      "type": "http",
      "url": "https://resos.usefulapi.io/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "resos": {
      "serverUrl": "https://resos.usefulapi.io/mcp"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "resos": {
      "type": "http",
      "url": "https://resos.usefulapi.io/mcp"
    }
  }
}

Tools this server provides (19)

Read directly from the server.

resos_list_bookings
List bookings, newest or oldest first as you sort, with date, time, party size, status, the guest's name, e-mail and phone, assigned tables and custom-field answers. Filter by date range, status, party size or guest name. The comment thread and sent-message log are not included (use resos_get_booking for the thread). Pages of at most 100; pass next_skip to read on. GET /bookings.
resos_get_booking
One booking by id, with the guest's contact data, tables, custom fields, payment, the comment thread (guest and restaurant messages) and the internal restaurant notes. GET /bookings/{id}.
resos_list_customers
List the restaurant's customers (guest profiles): name, e-mails, phones, city and country, tags, notes, flags, booking count and newsletter consent. The street address is not returned. Filter by name. Pages of at most 100. GET /customers.
resos_get_customer
One customer (guest profile) by id: contact data, tags, notes, flags, booking count and latest booking. GET /customers/{id}.
resos_list_guest_feedback
List guest feedback (ratings for food, service, value and atmosphere, whether they recommend, and the message). Filter by date range, or only submitted feedback. Pages of at most 100. GET /guestFeedback.
resos_get_guest_feedback
One guest feedback entry by id. GET /guestFeedback/{id}.
resos_list_seating_areas
List the seating areas with their tables (id, name, minimum and maximum seats) and table combinations. Use the ids for bookings and availability. GET /tables.
resos_list_opening_hours
List the opening hours: regular weekly hours (day 1 Monday to 7 Sunday) and special date-specific hours, each with id, name, open and close times and whether the restaurant is open. GET /openingHours.
resos_get_opening_hour
One opening-hour entry by id. GET /openingHours/{id}.
resos_list_custom_fields
List the custom booking fields (name, label, type, required, choices). Use the ids to read or set custom-field answers. GET /customFields.
resos_get_custom_field
One custom booking field by id. GET /customFields/{id}.
resos_get_available_dates
Dates in a range on which the restaurant is open for bookings (default: the next 30 days). GET /bookingFlow/dates.
resos_get_available_times
Booking times that are free on a date for a party size, optionally for one seating area. GET /bookingFlow/times.
resos_get_available_tables
The tables and table combinations that are free for a party size in a time window (UTC). Use it before assigning tables to a booking. GET /bookingFlow/availableTables.
resos_create_booking
WRITE: create a booking for a guest. It is a real booking in the restaurant's book. If notify_email or notify_sms is true, resOS e-mails or texts the GUEST (a confirmation); both default to false. Date and time are in the restaurant's local timezone. Check resos_get_available_times first: resOS may refuse a slot that is full or closed. It is not retried: if the call times out, read the bookings be
resos_update_booking
WRITE: change fields of an existing booking: date, time, party size, tables, duration, status, or the guest's name, e-mail or phone. Only the fields you pass change. A status change or a new time can make resOS e-mail or text the GUEST (for example on approved or declined). To cancel use resos_cancel_booking. It is not retried: after a timeout read the booking again before you try again. PUT /book
resos_cancel_booking
WRITE: cancel a booking (status canceled, with a canceled-at time). resOS may e-mail or text the GUEST a cancellation notice. The booking stays in resOS and can be read afterwards. Not retried: after a timeout read the booking first. PUT /bookings/{id}/cancel.
resos_add_booking_note
WRITE: add an internal restaurant note to a booking (for example `Birthday, bring a candle`). The guest does not see it and nothing is sent. At most 50 notes per booking; notes cannot be deleted through the API. Not retried: after a timeout read the booking first, or the note may be added twice. POST /bookings/{id}/restaurantNote.
resos_send_booking_comment
WRITE: post a comment from the restaurant on a booking's guest thread. The guest can see it. If send_notification is true, resOS e-mails or texts the GUEST the message now: you must choose true or false. At most 25 comments per booking and 5 per minute. Cannot be deleted through the API. Not retried: after a timeout read the booking first, or the guest may get it twice. POST /bookings/{id}/comment

resOS MCP by usefulapi FAQ

How do I add resOS MCP by usefulapi to Claude Code?

Run this command in your terminal: claude mcp add --transport http resos https://resos.usefulapi.io/mcp