Lets an assistant find restaurants on the Loyalist network, check table availability, book a table, check a booking, and join a waitlist.
What you can do
Find bookable venues across restaurant groups, optionally narrowed by signup form or another filter
Check bookable times at one venue for a date and party size, with slot IDs and venue-local start times
Book a table using a slot ID from the availability results
Read back a booking made with the same credential to confirm it landed
Ask to join a waitlist for a time the guest wants, without holding a table
When to use it
Useful when someone wants an assistant to check restaurant availability and make a reservation on the Loyalist network, or to be told about openings at a preferred time. It suits conversational dining plans where the venue, date, time and party size are settled before booking.
Requirements
A remote MCP endpoint at agent.eatloyalist.com over streamable HTTP; no login, packages, environment variables or headers are declared. The venue's local date and party size are needed for availability checks.
Before you install
Booking takes a real table at a real restaurant and there is no cancel tool, so a mistaken booking must be undone by the guest through the venue; confirm venue, date, time and party size with the person first and never book speculatively. A pending status is not a failure. A waitlist request is not a reservation and holds nothing.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.eatloyalist%2Frestaurant-reservations/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Restaurants bookable through this network, and what each one's system supports.
Returns every venue that has opted in, across restaurant groups. Two optional filters
narrow it, never widen it: `signup_form_id` to one website's venues when you found an
Orion signup embed on a restaurant's page, and `venue_id` to a single venue when
you already have its loyalist-venue-id (off a page's markup or a ReserveAction entry
point) and want just that one rather than listing them all and matching yourself.
Neither can reach a venue that has not opted in.
A venue with `bookable: false` has no reservation system connected and will return
no availability.
Parametersvenue_idsignup_form_id
get_availability
Check availability
Bookable times at one venue, on one date, for one party size.
`date` is the venue's own local calendar date, `YYYY-MM-DD`. Each slot carries a
`slot_id` to pass to book and a `starts_at` that is a full venue-local datetime, so
a service running past midnight is unambiguous without you having to infer the day.
An empty `slots` list means nothing is open on those terms, not that the venue is
closed. Try a different time, party size or date before telling someone it is full.
Book a table. This takes a real table at a real restaurant.
Pass a `slot_id` from get_availability. Confirm the venue, date, time and party size
with the person before calling this, and do not call it speculatively: there is no
cancel tool, so a booking made by mistake has to be undone by the guest phoning the
restaurant.
Calling it twice with identical arguments is safe and returns the same reservation
rather than taking a second table. Changing the slot or the guest makes it a
different booking, so re-read availability rather than editing the arguments to
"retry".
`phone` is optional here but required by some venues; omitting it can come back as
`guest_field_required`. `note` reaches the restaurant as the reservation's note.
`source` is where you found this venue: if the restaurant's own website told you a
value to pass (in its markup or llms.txt), send it here so the restaurant can see its
own site drove the booking. Leave it out if you did not arrive through one.
`reservation_id` is for your own use, to read the booking back with get_reservation.
It is not a confirmation number the venue knows, so do not read it out to the guest:
tell them the restaurant, date, time and party size instead.
Read one booking this credential made back from the venue.
Use it to confirm a booking landed. A `status` of `pending` means the venue has not
answered yet, not that it failed; treat anything you do not recognise as
non-terminal rather than reporting a failure.
Parametersreservation_idrequired
join_waitlist
Join the waitlist
Ask to be told if a table opens at a time the guest actually wants.
This is not a reservation and never becomes one by itself. The venue contacts the
guest if something frees up, so say that plainly rather than implying a table is
held.
Offer it whenever the guest cannot get a time that suits them, which is far more
often than a venue being completely full: someone who wants 7:30 and is offered
5:00 or 9:45 may well prefer to wait for 7:30. An empty get_availability is only
the most obvious case. Try other times, party sizes and dates first, then ask
whether they would rather wait than take a time that does not work. Record what
they wanted in `time_range`, not the time you found.
`date` is the venue's own local calendar date, `YYYY-MM-DD`. `time_range` is
required and is the window in the guest's words, like "7:00 PM - 9:00 PM" or
"7:00 PM"; ask the guest for it rather than guessing, because the venue works the
list by when people wanted to come. The email address is where the confirmation
goes, so it must be the guest's own.
Not every venue accepts these. One that does not refuses with a message saying so,
which is an answer, not an error to retry.
There is no reference number to give the guest, so the response is the only record
either of you gets. Confirm it back to them by the restaurant, date and time.
Mention the confirmation email only when `confirmation_sent` is true. When it is
false the request is still on the venue's list, the note simply did not go out, so
say they are on the list and that no email is coming rather than promising one.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.