yandex-eats-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YANDEX_EATS_DRY_RUN | No | If 'true', tools do not call the API | false |
| YANDEX_EATS_BASE_URL | No | Base URL for API (default: https://dc-partner.eda.yandex.net) | https://dc-partner.eda.yandex.net |
| YANDEX_EATS_CLIENT_ID | Yes | OAuth client id | |
| YANDEX_EATS_TIMEOUT_MS | No | Timeout in milliseconds (default: 30000) | 30000 |
| YANDEX_EATS_PARTNER_NAME | No | Sent as Partner-Name header (required for several write tools) | |
| YANDEX_EATS_CLIENT_SECRET | Yes | OAuth client secret |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| yandex_eats_auth_statusA | Check whether Yandex Eats Vendor Management credentials are configured and whether a cached OAuth token is valid. Never returns the access token. |
| yandex_eats_refresh_tokenA | Force-refresh the OAuth2 client-credentials token from POST /oauth2/token on dc-partner.eda.yandex.net. Does not return the token. |
| yandex_eats_orders_historyA | Fetch order history from Vendor Management (POST /v1/orders-history). Limits: max 1000 orders in the response; history retained for the last 180 days. Status filter values are NEW, CANCELLED, DELIVERED. |
| yandex_eats_orders_detailsA | Fetch detailed information for orders by Yandex eats_id list (POST /v1/get-orders-details). Max 100 ids per request; history retained 180 days. eats_id format: DDDDDD-DDDDDDDD. |
| yandex_eats_busy_mode_statusB | List restaurants with active high-demand (busy) status (POST /partner-integration/v1/place-info/v1/busy-mode-status). High demand adds extra cooking minutes. |
| yandex_eats_block_statusC | Get restaurant block status from Vendor Management (POST /v2/status). Requires Partner-Name. |
| yandex_eats_block_placesA | Block restaurant(s) in Yandex Eats (POST /block). Destructive. Requires confirm=true and Partner-Name. Tags: technical_problem | too_busy. If 'to' is omitted, block is indefinite. |
| yandex_eats_unblock_placesA | Unblock restaurant(s) (POST /unblock). Destructive. Requires confirm=true, Partner-Name, and blockIds from a prior block/status response. |
| yandex_eats_menu_importA | Force Yandex to re-parse the partner menu or stop-list (POST /menu/import/initiation). Requires Partner-Name. operationType: menu (default) or menu_stop_list. Safe to retry if unsure whether import started. |
| yandex_eats_validate_courier_codeB | Validate the courier pickup code for an order (POST /platform/orders/{orderId}/codes/validate). Requires Partner-Name. Sensitive operational tool. |
| yandex_eats_feedback_answerA | Reply to customer order feedback with text and optional promo percent (POST /feedback-answer). Subscription-gated — may return 403 without subscription. Promo values: 10, 15, 20, 30, 40. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| yandex_eats_investigate_order | Playbook to look up order history/details for a place and eats_id |
| yandex_eats_resync_menu | Playbook to force a menu or stop-list import for a restaurant |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| overview | Capabilities and configuration summary |
| config-status | Non-secret configuration and token cache status |
TDQS
Scored across 11 tools
Every tool has a clearly distinct purpose: auth management, order history versus details, restaurant block versus busy mode, menu import, courier validation, and feedback. No two tools overlap in functionality.
All tools follow the consistent prefix 'yandex_eats_' and use a clear verb_noun pattern (e.g., refresh_token, block_places, validate_courier_code). Naming is predictable and uniform.
With 11 tools, the server is well-scoped for managing Yandex Eats vendor operations. The count covers essential actions without being overwhelming or too sparse.
The tool set covers core vendor workflows (auth, orders, block/unblock, menu import, feedback) but lacks tools for listing all restaurants, getting restaurant details beyond block status, or managing menu items individually. Some operations require workarounds.