resOS MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

resOS MCP by usefulapi is answering right now. Last checked 8 min ago. It exposes 19 tools. Last commit 6 Nov 2026.

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

Uptime history 6 days of history

6 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

216 ms

Response time

average over 24h

Stars

last commit 6 Nov 2026

What changed 11

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 3 November 2026. No other catalogue keeps this.

7 Nov a tool changed version3 times that day

6 Nov a tool changed version3 times that day

5 Nov a tool changed version2 times that day

3 Nov a tool changed version3 times that day

and 7 more, back to 3 November 2026

Nothing serious here today

Today is the operative word: we check resOS MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://resos.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.resos]
url = "https://resos.usefulapi.io/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 19

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

resos

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_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_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 before you try again, or you may book twice. resOS may silently throttle the same e-mail, phone or IP creating more than 10 bookings in 24 hours. POST /bookings.

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_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_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_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_get_custom_field

One custom booking field by id. GET /customFields/{id}.

resos_get_customer

One customer (guest profile) by id: contact data, tags, notes, flags, booking count and latest booking. GET /customers/{id}.

resos_get_guest_feedback

One guest feedback entry by id. GET /guestFeedback/{id}.

resos_get_opening_hour

One opening-hour entry by id. GET /openingHours/{id}.

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_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_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_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_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_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_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_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 /bookings/{id}.

Endpoints

URL	Transport	State	Latency	Checked
https://resos.usefulapi.io/mcp	streamable-http	answering	260 ms	8 min ago

Alternatives to resOS MCP by usefulapi

same job, measured the same way

GoTable MCP by usefulapi

by usefulapi

Read availability, reservations, guests; create, change, cancel bookings; add notes in GoTable.

21 tools answering

Bookingmood MCP by usefulapi

by usefulapi

Read Bookingmood bookings, availability, guests, payments and invoices; update bookings, contacts.

21 tools answering

Appointedd MCP by usefulapi

by usefulapi

Read Appointedd bookings, customers and availability; create, change and cancel bookings.

20 tools answering

Appointo MCP by usefulapi

by usefulapi

Read Appointo bookings, availability and subscriptions; create, reschedule and cancel bookings.

10 tools answering

Acuity Scheduling MCP by usefulapi

by usefulapi

Read appointments, types, calendars and availability; create, cancel or reschedule bookings.

18 tools answering

Booqable MCP by usefulapi

by usefulapi

Browse rental orders, customers, products and availability, and create bookings in Booqable.

21 tools answering

HolidayPitches MCP by usefulapi

by usefulapi

Check pitch availability and bookings; create bookings and update their status in HolidayPitches.

7 tools answering

AgendaPro MCP by usefulapi

by usefulapi

Read AgendaPro bookings, slots, clients, services and sales; create, update and cancel bookings.

24 tools answering

resOS MCP by usefulapi — questions

Answers built from our own checks of this server.

What can resOS MCP by usefulapi do?

It exposes 19 tools, read directly from the server on our last check. Among them: resos_add_booking_note, resos_cancel_booking, resos_create_booking, resos_get_available_dates, resos_get_available_tables, resos_get_available_times and 13 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is resOS MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 216 ms. The bar chart above shows every period we have measured.

How do I connect resOS MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does resOS MCP by usefulapi need an API key?

No. resOS MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 19 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is resOS MCP by usefulapi?

It answers our handshake in 216 ms on average, which is faster than 66% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is resOS MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at resos.usefulapi.io, which runs on its operator's own terms.