Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Loyalist Reservations is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Book tables at restaurants on the Loyalist network. No login; read availability, then book.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http loyalist-reservations-mcp https://agent.eatloyalist.com/mcp
# 2 — ask your agent for something these tools do
# find_venues, get_availability, book and 2 more
Loyalist Reservations costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http loyalist-reservations-mcp https://agent.eatloyalist.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 a Loyalist signup embed on a restaurant's page, and venue_id to a single venue when you already have its loyalist-ve
| Parameter | Type | Required | Notes |
|---|---|---|---|
| signup_form_id | no | — | |
| venue_id | no | — |
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 te
| Parameter | Type | Required | Notes |
|---|---|---|---|
| venue_id | string | yes | — |
| date | string | yes | — |
| party_size | integer | yes | — |
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 ar
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slot_id | string | yes | — |
| first_name | string | yes | — |
| last_name | string | yes | — |
| string | yes | — | |
| phone | no | — | |
| note | no | — | |
| source | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reservation_id | string | yes | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| venue_id | string | yes | — |
| date | string | yes | — |
| party_size | integer | yes | — |
| first_name | string | yes | — |
| last_name | string | yes | — |
| string | yes | — | |
| time_range | string | yes | — |
| phone | no | — | |
| notes | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Loyalist Reservations or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Loyalist Reservations can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.