tabelog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TABELOG_MCP_HOME | No | Set to move the data folder. The data folder is ~/Library/Application Support/tabelog-mcp on macOS, %APPDATA%\tabelog-mcp on Windows, and ~/.local/share/tabelog-mcp on Linux. Set TABELOG_MCP_HOME to move it. | |
| TABELOG_MCP_CHROME | No | Set to use another Chrome or Chromium binary. Install Google Chrome, or set TABELOG_MCP_CHROME. |
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 |
|---|---|
| tabelog_statusA | Where data is stored, whether this browser profile is signed in to Tabelog, and when the sign-in expires (read from Tabelog's session cookie at sign-in). Starts Chrome in the background if needed. |
| tabelog_loginA | Optional: sign in ahead of time. prepare_booking already signs in by itself when needed. Opens the Chrome window on Tabelog's login page and waits while the user signs in (LINE, Apple, Google, …). The user types credentials and codes themselves; this tool never sees them. The session is saved in the local browser profile. |
| find_areaA | Tabelog's own suggestions for a Japanese place name: stations, towns, and areas. Use when a search's resolved_area looks wrong. |
| search_restaurantsA | Search restaurants with Tabelog's filters. With date, time, and party, each result lists the online-booking times Tabelog shows around that time. 20 results per page; total is Tabelog's count. |
| find_available_restaurantsA | The main search for business dinners. Finds restaurants within walking range of every location, bookable online for the party on the next days within a time window, optionally with a private room, and returns each one's walking minutes and open times. Unset options come from saved preferences (dinner 17:00-20:00, business: private room, 15 minutes). Walking time is estimated from map distance, not transit. Takes 30 s to 2 min. |
| set_preferencesA | Saves a lasting preference the user stated, used as the default for later searches and bookings: seating windows, party size, private room, walking limit, budget, or a free-text note. |
| get_restaurantB | Tabelog's information table for one restaurant: genre, address, hours, closed days, budget, payment, seats, private rooms, smoking. |
| get_availabilityA | The booking calendar (each day open, few_left, or full). With date: which party sizes are open that day. With date and party: the bookable times. |
| prepare_bookingA | Fills Tabelog's booking form up to, never through, the final button. Signs in first if needed (a Chrome window opens for the user). Returns status ready with a summary and a single-use confirmation_token (5 minutes), or choose_plan (call again with plan), needs_login (sign-in still open), or needs_user (card, code, or unknown field: the user finishes). Books nothing. |
| confirm_bookingA | Places the booking prepared by prepare_booking. Only call after the user has seen that summary and said yes. Fails without a live token, or when the confirmation page changed since prepare. Reports confirmed only when Tabelog's completion page is seen. |
| show_booking_windowA | Brings the Chrome window with the current booking on-screen, so the user can finish a needs_user booking by hand. |
| get_booking_historyB | Past bookings made through this server, newest first: status, restaurant, date, party, plan, price, notes, failure reason. |
| get_preferencesA | Saved preferences (what the user said: seating windows, party, private room, walking limit, budget, notes) and learned ones (from confirmed bookings: usual genres, areas, party, time, repeat restaurants). |
| add_booking_noteB | Saves something the user said about a booking (how it went, who came, what to change next time) to the local history. |
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 14 tools
Most tools have clearly distinct purposes, and the prepare/confirm booking split is especially clear. The main overlap is between search_restaurants, find_available_restaurants, and get_availability, which all deal with availability/search and could be confused despite helpful descriptions.
The set is mostly consistent snake_case with action-oriented names like search_restaurants, prepare_booking, and get_availability. Minor deviations are the tabelog_ prefix on tabelog_status/tabelog_login and the mix of verbs such as find, get, search, and show.
Fourteen tools is well within the appropriate range for a restaurant search and booking assistant. Each tool maps to a clear role: status/login, search, restaurant detail, availability, booking preparation/confirmation, preferences, and history.
The surface covers search, availability, restaurant details, sign-in, booking preparation/confirmation, preferences, and history well. However, booking lifecycle coverage is incomplete: there is no tool to cancel or modify/reschedule an existing booking, which are notable missing operations for a booking-focused server.