easytable-mcp
Related Servers
Alternatives to easytable-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceAn MCP server for restaurant discovery and booking across Resy and OpenTable via natural language. It integrates Google Places data with dietary preferences, visit history, and weather awareness to provide personalized dining recommendations and group reservation management.23-
- AlicenseNot gradedqualityDmaintenanceMCP server that transforms Gurunavi into a browser-driven semantic proxy, providing restaurant search, details, and reservation management through normalized interfaces with safety controls.MIT
- FlicenseAqualityDmaintenanceMCP server for the Rizerve direct booking platform. Enables managing properties, bookings, availability, iCal sync, analytics, and webhooks through AI assistants.191-
- FlicenseNot gradedqualityAmaintenanceMCP server for NYC Restaurant Week, enabling search and lookup of participating restaurants, date checks, and filter options.-
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to manage restaurant reservations through typed MCP tools, including checking table availability, creating and canceling reservations, and listing the day's confirmed bookings.-
- AlicenseNot gradedqualityCmaintenanceThis MCP server enables an AI receptionist to manage field-service bookings end-to-end: checking technician availability from live Outlook calendars, sending asynchronous SMS offers, tracking request status, and creating confirmed Outlook events with ETag-locked concurrency, all without customer sign-in.MIT
TDQS
Scored across 8 tools
Each tool has a distinct action: booking CRUD (find/create/modify/cancel), availability lookups (list_types/list_dates/list_times), and diagnostics (healthcheck). The three list_* tools are related but clearly differentiated by what they enumerate (areas, dates, times), and descriptions reinforce their distinct purposes.
All tools use a consistent easytable_ namespace with a predictable verb_noun pattern (find_bookings, cancel_booking, create_booking, modify_booking, list_types, list_dates, list_times). Only healthcheck is a bare noun, a trivial deviation that doesn't break the pattern.
Eight tools is well-scoped for a restaurant-booking server, covering the booking lifecycle plus availability and a bridge diagnostic. No redundant or padding tools.
Full booking lifecycle is covered (create/read/modify/cancel) plus the availability trio needed to book. Gaps are minor: no restaurant-discovery/search tool to find a venue id, but the widget-tab workflow suggests that's handled externally.