easytable-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| easytable_list_typesA | List the bookable areas/types for a restaurant (e.g. "Boka Inne", "Boka baren"). Returns each area's type id for use in the other availability tools. |
| easytable_list_datesA | List bookable dates for a restaurant area and party size. Each entry has an ISO date and whether it is available. |
| easytable_list_timesA | List available time slots for a restaurant area, date, and party size. Times are returned as HH:MM. |
| easytable_find_bookingsA | Look up a restaurant's existing bookings made with a given mobile number. Returns each booking's id (for easytable_cancel_booking) plus a summary. |
| easytable_cancel_bookingA | Cancel an existing booking. Look up the booking id first with easytable_find_bookings (it needs the mobile the booking was made with). Without confirm: true it returns a dry-run preview and makes NO network call; with confirm: true it cancels. |
| easytable_create_bookingA | Create a restaurant booking. Reads the Cloudflare Turnstile token from your signed-in booking-widget tab (via the bridge) and submits it with the reservation — so a book.easytable.com/book/?id= tab must be open and loaded. Without confirm: true it returns a dry-run preview and makes NO network call; with confirm: true it books. |
| easytable_modify_bookingA | Modify an existing booking (date/time/party size/details). Like create, it reads the Turnstile token from your signed-in widget tab. Get the existing booking id from easytable_find_bookings. Without confirm: true it returns a dry-run preview and makes NO network call; with confirm: true it applies the change. |
| easytable_healthcheckA | Round-trips a small public book.easytable.com URL (/robots.txt) through the fetchproxy bridge and returns diagnostics: the bridge's role (host/peer/null), port, version, the extension link (linked / pair pending / not attached / never answered), the elapsed round-trip time, and a plain-English hint distinguishing 'bridge never came up' from 'extension not connected' from 'real book.easytable.com-side problem'. Read-only, no auth required. Call this when a real tool fails and you want to know which hop broke. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: availability lookup (list_dates/list_times/list_types), booking lifecycle (create/find/modify/cancel), and diagnostics (healthcheck). No two tools overlap in function.
Most tools follow a consistent verb_noun pattern (list_dates, create_booking, cancel_booking, find_bookings, modify_booking). The single-word healthcheck deviates slightly but is still understandable and not confusing.
Eight tools is well-scoped for a restaurant booking MCP server. The count covers the core booking lifecycle, availability checks, and a useful diagnostic without bloat.
The tool surface covers the full booking workflow: discover types/dates/times, create bookings, look up existing bookings by mobile, modify, and cancel. The healthcheck tool also fills the obvious debugging gap for bridge-related failures.