Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Tableall is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
10
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Access Japan's finest Michelin-starred restaurants. Search, check availability, and browse menus.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport sse tableall-mcp https://mcp.tableall.com/sse
# 2 — ask your agent for something these tools do
# search_restaurants, get_restaurant_details, get_restaurant_menu and 7 more
Tableall costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TAAll 1 server
tableall1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is sse, as the publisher's own manifest declares it.
claude mcp add --scope user --transport sse tableall-mcp https://mcp.tableall.com/sseReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Browse restaurants by region, cuisine, or area. Returns a directory-style list with name, location, Michelin stars, and starting price. Does not include real-time availability — for date-based searches use search_available_restaurants, and for one restaurant's openings use check_availability. For a specific named restaurant, use this tool to obtain its restaurant_id, then call get_restaurant_deta
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prefecture | string | no | Prefecture/region filter. Available values: Tokyo, Kyoto, Osaka, Sapporo, Kanazawa, Komatsu, Toyama, Fukuoka, Nagoya, Ise Shima, Kobe, Niseko, Shizuoka, Nagano, Hiroshima, Shikoku, Niigata |
| genre | string | no | Cuisine type. Available options: "Sushi", "Kaiseki", "Tempura", "Wagyu", "Italian", "French", "Chinese", "Innovative", "Spanish", "Yakiniku", "Yakitori", "Teppanyaki", "Unagi", "Dessert Dining", "Kush |
| area | string | no | Specific area within prefecture (e.g., "Ginza", "Shibuya") |
| offset | number | no | Number of restaurants to skip for pagination (default: 0). Only use this if the user explicitly asks to see additional results beyond the initial 30. |
Get the full profile of one specific restaurant: untrimmed description, booking_rules, booking_tips, address, operating_hours, seating, and starting price. Use when the user names a specific restaurant and wants its details, or when you have a restaurant_id and need fields that search_restaurants does not return. Does not return menu or courses (use get_restaurant_menu), cancellation policy (use
| Parameter | Type | Required | Notes |
|---|---|---|---|
| restaurant_id | number | yes | The unique ID of the restaurant |
Get the menu for a specific restaurant: an array of course names and their prices. Use when the user asks about a specific restaurant's menu, courses, or course pricing. This tool returns course names and prices only — not dish lists, course composition, number of pieces, or ingredients. For full course details, direct the user to the restaurant page (details_url in the response). The response i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| restaurant_id | number | yes | The unique ID of the restaurant |
Check real-time availability for one specific restaurant within a date range. Returns all openings for that restaurant; it does not filter by time of day. Use when you already know which restaurant the user wants. If the user is browsing across multiple restaurants in a region or cuisine, use search_available_restaurants instead. Use the exact parameter names start_date, end_date, restaurant_id,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | no | Start date in YYYY-MM-DD format |
| end_date | string | no | End date in YYYY-MM-DD format |
| restaurant_id | number | no | Specific restaurant ID (optional) |
| daily_or_minutes | string | no | Time granularity - "daily" for daily view or "minutes" for minute-level detail |
| by_menu_item | boolean | no | Group availability by menu items |
| num_people | number | no | Number of people/party size (optional) |
Search across multiple restaurants for availability within a date range. Returns restaurants that have openings, filterable by prefecture, area, genre, and party size. Use when the user does not yet have a specific restaurant in mind and is browsing or filtering by region or cuisine. If the user already has a specific restaurant, use check_availability instead. Date handling: if the user gives o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | yes | Start date in YYYY-MM-DD format (required) |
| end_date | string | yes | End date in YYYY-MM-DD format (required) |
| prefecture | string | no | Prefecture/region filter. Values not in the allowed list will be ignored. |
| area | string | no | Specific area within prefecture (e.g., "Ginza", "Shibuya") |
| genre | string | no | Cuisine type (e.g., "Sushi", "Kaiseki", "French", "Italian") |
| num_people | number | no | Number of guests to filter availability |
| limit | number | no | Maximum number of restaurants to return (default: 20, max: 100) |
| offset | number | no | Number of restaurants to skip for pagination (default: 0) |
Read-only: retrieve a restaurant's cancellation policy. This tool only reads policy data; it does not cancel or modify any reservation. Safe to call repeatedly. Use when the user asks about the cancellation policy, refund terms, or no-show fee, or before calling create_reservation or create_reservation_request. get_restaurant_details returns booking_rules and booking_tips, which describe when bo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| restaurant_id | number | yes | Restaurant ID to retrieve cancellation policies for |
| course_id | string | no | Course external ID (optional, for course-specific policies) |
Create a direct reservation for a specific available opening (opening_id required). Use after check_availability has returned an opening and the user has chosen which opening_id to book. If check_availability returned no openings, use create_reservation_request instead. Flow (summary — see resource tableall://flow/direct-reservation for full details): 1. Call get_cancellation_policies and explai
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | User email address (always required) | |
| first_name | string | no | User first name / 名 (required for new users or users with incomplete profile) |
| last_name | string | no | User last name / 姓 (required for new users or users with incomplete profile) |
| country | string | no | Country code ISO 3166-1 alpha-2, e.g., "JP", "US" (required for new users or users with incomplete profile) |
| phone_country_code | string | no | Phone country code, e.g., "+81" (required for new users or users with incomplete profile) |
| phone | string | no | Phone number without country code (required for new users or users with incomplete profile) |
| opening_id | string | yes | Opening external ID from check_availability (required) |
| course_id | string | yes | Course external ID (required) |
| party_size | number | no | Number of guests. Must match fixed_seats for fixed openings, or be within min/max range for flexible openings. |
| special_request | string | no | Special requests or notes for the restaurant |
| allergies | string | no | Allergy information |
| preferences | string | no | Food preferences |
| dislikes | string | no | Food dislikes |
| coupon_code | string | no | Coupon code for discount (optional) |
| ai_client | string | yes | AI client name. You MUST provide your AI model name (e.g., "Claude", "Gemini", "GPT", "Copilot"). |
Check the status of a reservation by session ID. Requires the access_token that was returned in the create_reservation response. You MUST have stored the access_token from the create response to use this tool. Without a valid access_token, the API will return 403 Forbidden. IMPORTANT - PRICE DISPLAY: The "price" field already INCLUDES the "booking_fee". Do NOT add them together. When displaying
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | Reservation session ID returned from create_reservation |
| access_token | string | yes | Access token returned from create_reservation response (data.access_token). Required for authorization. |
Submit a reservation request for a selected restaurant, dates, time range, and party size. Use after check_availability or search_available_restaurants has been run and the user confirms they want to submit a request. Use this when the user prefers dates or times other than the available openings, or when no openings were found and the user wants to request one. The user's use of the word "reques
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | User email address (always required) | |
| first_name | string | no | User first name / 名 (required for new users or users with incomplete profile) |
| last_name | string | no | User last name / 姓 (required for new users or users with incomplete profile) |
| country | string | no | Country code ISO 3166-1 alpha-2, e.g., "JP", "US" (required for new users or users with incomplete profile) |
| phone_country_code | string | no | Phone country code, e.g., "+81" (required for new users or users with incomplete profile) |
| phone | string | no | Phone number without country code (required for new users or users with incomplete profile) |
| restaurant_id | number | yes | Restaurant ID (required) |
| course_id | string | yes | Course external ID (required) |
| num_adults | number | yes | Number of adults (required). If user only says total number of guests (e.g., "3 people"), treat all as adults. |
| num_children | number | yes | Number of children (required). Default to 0 if user does not specify children count or only provides total guest count. |
| dates | array | yes | Preferred dates in YYYY-MM-DD format. Can specify multiple dates. |
| start_time_from | string | yes | Preferred start time from, in HH:mm format (e.g., "18:00"). Japan Time (JST). |
| start_time_to | string | yes | Preferred start time to, in HH:mm format (e.g., "20:00"). Japan Time (JST). |
| special_request | string | no | Special requests or notes for the restaurant |
| allergies | string | no | Allergy information |
| preferences | string | no | Food preferences |
| dislikes | string | no | Food dislikes |
| hotel_name | string | no | Hotel name (optional) |
| comment | string | no | Additional comments (optional) |
| coupon_code | string | no | Coupon code for discount (optional) |
Check the status of a reservation request by session ID. Requires the access_token that was returned in the create_reservation_request response. You MUST have stored the access_token from the create response to use this tool. Without a valid access_token, the API will return 403 Forbidden. IMPORTANT - PRICE DISPLAY: The "price" field already INCLUDES the "booking_fee". Do NOT add them together.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | Reservation request session ID returned from create_reservation_request |
| access_token | string | yes | Access token returned from create_reservation_request response (data.access_token). Required for authorization. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Tableall or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Tableall can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.