Hotpepper MCP Server

Hotpepper MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. ホットペッパーグルメ MCP Server.

What you get

ホットペッパーグルメ MCP Server

What the assistant can call

Once Hotpepper is connected, these are the calls the assistant has available:

• Homebrew — The Homebrew tool exposed by this server
• gourment_search — The gourment_search tool exposed by this server
• shop_search — The shop_search tool exposed by this server
• large_area_search — The large_area_search tool exposed by this server
• middle_area_search — The middle_area_search tool exposed by this server
• small_area_search — The small_area_search tool exposed by this server
• genre_search — The genre_search tool exposed by this server
• dinner_budget_master_search — The dinner_budget_master_search tool exposed by this server
• large_service_area_master_search — The large_service_area_master_search tool exposed by this server
• service_area_master_search — The service_area_master_search tool exposed by this server
• credit_card_master_search — The credit_card_master_search tool exposed by this server
• dinner_budget_master — The dinner_budget_master tool exposed by this server

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need one environment variable: HOTPEPPER_GOURMET_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Hotpepper's toolset — Homebrew, gourment_search, shop_search and 11 more — is a fair guide to whether it matches your workflow. It is maintained by miyamo2; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Hotpepper.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the hotpepper mcp server does with a few real requests.