meican-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | 默认3000 | |
| BIND_HOST | No | 默认127.0.0.1 | |
| LOG_LEVEL | No | 默认info | |
| MCP_API_KEY | No | HTTP /mcp 的Bearer token | |
| MEICAN_CLIENT_ID | No | 美餐的OAuth client id | |
| MEICAN_NAMESPACE | No | 默认组织/站点 namespace | |
| MEICAN_ACCESS_TOKEN | No | 美餐sat cookie | |
| MEICAN_API_BASE_URL | No | 默认 https://www.meican.com/forward/api | |
| MEICAN_CLIENT_SECRET | No | 美餐的OAuth client secret | |
| MEICAN_REFRESH_TOKEN | No | 美餐srt cookie |
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 |
|---|---|
| meican_whoamiA | Look up the current user's organization info and ALL delivery addresses on Meican. Call this once per user to discover their |
| meican_list_meal_tabsA | List meal sessions ('餐次', e.g. 午餐, 晚餐) available for a given date. Each tab has a |
| meican_list_restaurantsA | List restaurants serving in one meal session. Returns each restaurant's |
| meican_show_menuA | Show one restaurant's full menu for a meal session. Returns dishes grouped by section. You need |
| meican_list_ordersA | List the current user's existing Meican orders for a date plus any unpaid items. Call this BEFORE |
| meican_show_orderA | Show full status of one order by its uniqueId, including pickup location, current pay status, and dishes. Use after placing an order to confirm it succeeded (expect status_info='NEW_ORDER', pay_status='SUCCESS'). |
| meican_place_orderA | Place a meal order. DESTRUCTIVE: this may charge the user or consume an organization subsidy. ALWAYS confirm dish names, counts, total price, target time, and pickup address with the user BEFORE calling this. Set |
| meican_cancel_orderA | Cancel a meal order. DESTRUCTIVE: this removes the order. ALWAYS confirm with the user before calling. |
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 8 tools
Each tool has a clearly distinct purpose: cancel, list tabs, list orders, list restaurants, place order, show menu, show order details, and look up user info. No two tools have overlapping functionality.
All tools follow the consistent pattern 'meican_verb_noun' with snake_case, making it easy to predict tool names and understand their actions.
8 tools is appropriate for a meal ordering service, covering essential actions without being overwhelming or too sparse.
The set covers the full ordering lifecycle: browsing sessions, restaurants, menus, placing orders, viewing orders, and canceling. A minor gap is the lack of an update/modify order tool, but core workflows are well-supported.