Restaurant Booking MCP Server
Related Servers
Alternatives to Restaurant Booking MCP Server
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-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that integrates with Google Places API to enable AI clients to search for restaurants and get food recommendations based on location and preferences.1-
- FlicenseNot gradedqualityNot gradedmaintenanceAn AI-native restaurant discovery service that enables searching and receiving natural language recommendations for over 2,200 restaurants across 15+ US cities. It provides tools for accessing detailed restaurant info, curated lists, and cuisine-specific searches through the Model Context Protocol.-
- AlicenseNot gradedqualityDmaintenancePersonalized restaurant recommendations, table bookings, and delivery via MCP, CLI, or API, learning user taste and acting proactively.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to order food from TGO Yemek by browsing restaurants, managing carts, and completing checkouts. It allows users to handle address selection and order tracking directly through natural language interactions.2913MIT
- AlicenseAqualityDmaintenanceA server that enables AI models to fetch and display Google Street View imagery, allowing users to create virtual tours by viewing streets and landmarks from anywhere.47MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: check_availability verifies reservation slots, get_booking_instructions provides procedural guidance, get_restaurant_details offers venue information, make_reservation books a table, and search_restaurants finds restaurants. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern with snake_case: check_availability, get_booking_instructions, get_restaurant_details, make_reservation, and search_restaurants. The naming is predictable and uniform throughout.
With 5 tools, the server is well-scoped for restaurant booking, covering key operations like search, details, availability, reservation, and instructions. Each tool earns its place without being too sparse or bloated.
The tool set covers core workflows: search, get details, check availability, make reservation, and get instructions. A minor gap exists in update/cancel reservation operations, but agents can work around this for basic booking tasks.