MCP.Market

Gerezi MCP server

by nicklasmenschel·io.github.nicklasmenschel/gerezi-mcp·v0.1.3

Manage restaurant bookings via Claude — read covers, find guests, move tables, send wedding quotes.

C55/100grade C
What users say
No reviews yet
Be the first
Safety scan
C55/100

full report

Adoption
New

19 downloads/wk

Reviews

Write one

Nobody has reviewed Gerezi yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Gerezi tools (15, 6 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • add_internal_note

    Add a private staff note to a booking. Distinct from the guest-visible specialRequests. Useful for 'allergic to nuts', 'big spender', 'celebrating 50th birthday'. Visible to staff on the dashboard popover but never sent to the guest.

  • cancel_bookingwrite action

    Cancel a booking. Refund (if applicable) is computed by the platform. Pass a clear reason — it lands in the audit row. Set notify_guest=false for abandoned-cart cleanups.

  • cancel_deviswrite action

    Cancel a devis that hasn't been accepted yet. Reason is stored in the audit timeline.

  • change_party_size

    Adjust the party size on an existing booking. Use when a guest calls to say their party went from 8 to 6, etc.

  • create_bookingwrite action

    Create a new booking on the connected restaurant's calendar. Use this for placeholder bookings (operator blocking a date), private events, or recording a phone-in reservation. The booking is CONFIRMED on creation. If table_id is provided, the tool also PATCHes the booking to assign that table. Up to 50 guests per single booking.

  • create_deviswrite action

    Create a quote (devis) for a private event. Supports multi-option quotes (Option A / B / C) with multi-rate VAT line items. Customer can be looked up by guest_id or upserted by email. Set send=true to immediately email the customer; otherwise the devis is created in DRAFT for operator review.

  • find_booking_by_guest_name

    Search recent bookings by a guest's name. Returns matching bookings with their date/time, party size, status, and contact info. Useful for 'find Julie Kohlhoff's booking', 'when is the wedding party scheduled?', etc.

  • get_restaurant_summary

    Snapshot of the connected restaurant: today's confirmed covers, abandoned-cart leads to chase, recent no-shows, and total bookings this week. Use this for the morning briefing or any 'how are we doing' question.

  • list_bookings_for_date

    List all bookings on a specific date for the connected restaurant. Returns guest name, party size, table assignment, status (including PENDING_PAYMENT for abandoned carts), source (ONLINE / MANUAL / PHONE / WALK_IN), and any special requests. Use this for daily prep, briefings, or 'who's in tonight'-style questions.

  • list_recent_staff_overrides

    List staff overrides from the last N days — bookings that were force-overbooked into full slots, or modifications made inside the cancellation window. Each entry shows what changed, when, and which staff member did it. Use this for the daily/weekly audit review.

  • move_booking

    Move a booking to a new datetime. Looks up the booking by booking_number, then calls the platform's move endpoint. Sends the standard BOOKING_MODIFIED email to the guest unless notify_guest=false. Set force_override=true only when intentionally overbooking a full slot.

  • revise_devis

    Spawn a new draft version of a sent devis. Use when the customer asks for changes ('drop the wine pairing', 'add a vegan option').

  • search_guests

    Search the restaurant's guest CRM by name, email, or phone fragment. Returns matching guests with their booking count, last visit, VIP status, allergies, and internal notes. Use this for 'has this customer been here before?', 'pull up the regulars'.

  • send_deviswrite action

    Send a DRAFT devis to the customer. Transitions the version to SENT (becomes immutable) and fires the customer email with the public link.

  • update_booking_contactwrite action

    Update the guest-contact fields on an existing booking (name, email, phone). Use when a placeholder booking was created with a stand-in email and the real customer info comes in later. Only the fields you provide are changed.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancerepository not readable: repo not found3/15
  • Maintainer identityno repository or website to verify2/10
Overall 55/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Gerezi compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
55/100
higher than 10% of 48,255 servers
Tools
15
the typical server has 7
Tools that change things
40%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
19
more than 6% of 12,191 servers with a package

What its tools let an agent do: 7 read · 3 create · 2 change · 2 delete · 1 send or post

Install Gerezi in Claude Code, Cursor or VS Code

Runs npx -y @gerezi/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add gerezi-mcp -- npx -y @gerezi/mcp
Add to Cursor

Gerezi: common questions

Is Gerezi MCP server safe?
With care: it is graded C, so read the findings first (55/100). Read the Gerezi safety report
How do I install Gerezi?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Gerezi need an API key?
Yes. The registry entry asks for GEREZI_API_KEY.
Is Gerezi maintained?
The latest release is v0.1.3.
How does Gerezi compare with other MCP servers?
safety score 55/100 (higher than 10% of 48,255 servers); tools 15 (the typical server has 7); tools that change things 40% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.