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_typesB | 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). Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The first call makes NO network call. |
| 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. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The first call makes NO network call. |
| 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. The change replaces the whole booking: email, comment and company are required — pass the booking's current values to keep them (ask the user if unknown), or '' to clear them; the newsletter opt-in is reset. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The first call makes NO network call. |
| easytable_healthcheckA | Round-trips a small public book.easytable.com URL (/robots.txt) through ContextMint Bridge (your signed-in browser tab) 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 'this browser can't serve a capability' 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 targets a distinct booking lifecycle action or availability query; create/modify/cancel/find are clearly differentiated, and list_dates/list_times/list_types have separate resource scopes. healthcheck is a diagnostic outlier but clearly separate from booking operations.
All tools use the easytable_ prefix and snake_case; booking actions follow verb_noun (cancel_booking, create_booking, etc.) and availability tools follow list_noun. healthcheck is a minor deviation as a single compound noun rather than verb_noun.
8 tools is well-scoped for a restaurant booking integration, covering booking lifecycle, availability lookups, and diagnostics without bloat. Each tool has a clear role and earns its place.
Covers create, modify, cancel, find bookings, and availability listing (types/dates/times) plus healthcheck. Minor gap: no get_booking tool to fetch full booking details (email/comment/company) needed by modify, though find_bookings summary plus user prompting may suffice.