Gerezi MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add gerezi-mcp -e 'GEREZI_API_KEY=<GEREZI_API_KEY>' -- npx -y @gerezi/mcp

{
  "mcpServers": {
    "gerezi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@gerezi/mcp"
      ],
      "env": {
        "GEREZI_API_KEY": "<GEREZI_API_KEY>"
      }
    }
  }
}

[mcp_servers.gerezi-mcp]
command = "npx"
args = ["-y", "@gerezi/mcp"]
env = { GEREZI_API_KEY = "<GEREZI_API_KEY>" }

{
  "mcpServers": {
    "gerezi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@gerezi/mcp"
      ],
      "env": {
        "GEREZI_API_KEY": "<GEREZI_API_KEY>"
      }
    }
  }
}

{
  "servers": {
    "gerezi-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@gerezi/mcp"
      ],
      "env": {
        "GEREZI_API_KEY": "<GEREZI_API_KEY>"
      }
    }
  }
}

Put your own value in place of <GEREZI_API_KEY> (Your Gerezi API key (tbl_live_*). Get one from https://www.gerezi.com/settings/api-keys). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: GEREZI_API_URL (Gerezi API base URL. Defaults to https://www.gerezi.com — only override for self-hosted Gerezi installs), GEREZI_RESTAURANT_SLUG (Optional restaurant slug for logging context. The API key already scopes the request to your restaurant), GEREZI_MCP_PHASE (Which tool surface to expose. "1" = read-only (5 tools). "2" = read+write (15 tools, includes booking creation, cancellation, quotes). Defaults to "1").