Dianping MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DP_CITY | No | search_places 未传城市时的默认城市 | 上海 |
| DP_HEADLESS | No | MCP 搜索是否无头运行；登录请使用 npm run login | true |
| DP_PROFILE_DIR | No | 浏览器登录资料目录 | ~/.dianping-mcp/browser-profile |
| DP_CACHE_TTL_MS | No | 搜索和详情的内存缓存时间（毫秒） | 300000 |
| DP_MIN_INTERVAL_MS | No | 两次页面请求的最小间隔（毫秒） | 1500 |
| DP_NAVIGATION_TIMEOUT_MS | No | 页面导航和选择器超时（毫秒） | 25000 |
| DP_BROWSER_EXECUTABLE_PATH | No | Chrome/Edge/Chromium 可执行文件路径，默认自动探测 |
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 |
|---|---|
| search_placesA | 按城市和关键词搜索大众点评上的餐厅、景点、酒店或其他本地商户。 |
| get_place_detailsA | 根据搜索结果中的店铺 ID 或 URL 读取地址、电话、营业时间、评分及精选评论。 |
| check_sessionA | 检查本地浏览器、登录状态及是否需要完成安全验证。 |
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 3 tools
The three tools have clearly distinct purposes: searching for places, retrieving detailed info about a specific place, and checking session/authentication status. No overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern in snake_case (search_places, get_place_details, check_session), making the naming predictable and easy to understand.
With 3 tools, the server is concise but covers the core functionality of searching and retrieving details for a local services platform. The inclusion of a session-check tool is practical, and the count feels appropriate for the scope.
The tool surface covers the essential read operations—search and detail retrieval—along with session verification. For a read-oriented API, this is reasonably complete. Minor gaps like listing categories or handling pagination could exist but are not critical.