
Gerezi Mcp
io.github.nicklasmenschelPublished by GitHub account nicklasmenschelv0.1.3Updated Oct 27, 2026
Manage restaurant bookings via Claude — read covers, find guests, move tables, send wedding quotes.
Overview
Local MCP server that lets an assistant read and manage restaurant bookings, covers, guests, tables and wedding quotes through the Gerezi API.
- What you can do
- Read restaurant booking data such as covers, guests and tables
- Look up guests and move bookings between tables
- Create and cancel bookings and send wedding quotes when the write phase is enabled
- Switch between a read-only surface of 5 tools and a read+write surface of 15 tools via a phase setting
- When to use it
- Useful for restaurant operators already on Gerezi who want an assistant to answer questions about bookings and, if enabled, make booking changes and send quotes without opening the dashboard.
- Requirements
- Runs locally over stdio from the npm package @gerezi/mcp, so Node.js is needed. Requires a Gerezi API key in GEREZI_API_KEY; GEREZI_API_URL defaults to the hosted service and only needs overriding for self-hosted installs. Optional GEREZI_RESTAURANT_SLUG for logging context. Desktop only.
Installation
In SourceWeft
- Open Gerezi Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.3LatestSep 16, 2026
Score
25% of the applicable checks met
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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.