Skip to main content
Glama
horse-3903

Tabelog MCP Server

by horse-3903

Related Servers

Alternatives to Tabelog MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching restaurants on Tabelog and retrieving details, reviews, menus, ratings, photos, and online-booking availability as MCP tools, without a browser.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to concurrently search, normalize, and compare Japanese restaurant results across Tabelog, Hot Pepper Gourmet, and Google Maps, with filters for cuisine, area, reservations, and amenities. It also retrieves structured restaurant details, reviews, menus, and courses through typed MCP tools.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude, Codex, Cursor, or any MCP client to find restaurants in Japan by location, walking time, party size, private room, cuisine, budget, and seating window, returning real availability for the requested date. It books them in two steps through the user's own signed-in Chrome, preparing a summary and confirmation token first and placing the reservation only after the user approves it.
      14
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables Claude and other AI assistants to search restaurants, manage bookmarks, and read guides on a user's Beli account. Supports restaurant lookup, bookmark creation and status checks, guide browsing, and a read-only passthrough to any GET endpoint.
      10
      MIT

    TDQS

    B3/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: restaurant detail vs reviews/menu/photos/vacancy, hierarchical area tools, and search/autocomplete. The only overlap is tabelog_get, which can reach any GET endpoint and could compete with dedicated tools, but it is explicitly framed as an escape hatch.

    Naming Consistency3/5

    The names use several conventions: verb_noun (search_restaurants, suggest_search), resource_noun (restaurant_reviews), noun_detail (restaurant_detail), area_level1/2, and bare nouns like stations. They remain readable, but the pattern is not predictable.

    Tool Count5/5

    12 tools is well-scoped for a restaurant discovery/detail server. Each tool maps to a meaningful step: location resolution, search/autocomplete, restaurant details, subresources, nearby popularity, and a generic read escape hatch.

    Completeness4/5

    The surface covers area hierarchy, stations, autocomplete, search, restaurant detail, reviews, menu, photos, vacancy, and nearby popularity. Minor gaps include an explicit genre taxonomy listing and reservation/booking actions, but the read-only escape hatch mitigates missing GET coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues