Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@yandex-eats-mcp show my order history for yesterday"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for the Yandex Eats Vendor Management API.
Lets AI agents (Cursor, Claude Desktop, and other MCP hosts) manage partner operations: orders history/details, busy mode, place blocks, menu import, courier code validation, and feedback replies.
This wraps the push Vendor Management API (
https://dc-partner.eda.yandex.net). It is not a consumer ordering API.
{
"mcpServers": {
"yandex-eats": {
"command": "npx",
"args": ["-y", "yandex-eats-mcp"],
"env": {
"YANDEX_EATS_CLIENT_ID": "your-client-id",
"YANDEX_EATS_CLIENT_SECRET": "your-client-secret",
"YANDEX_EATS_PARTNER_NAME": "your-partner-name"
}
}
}
}Pin a version: "args": ["-y", "yandex-eats-mcp@0.1.0"].
npm install
npm run build
npm startMCP config pointing at a local build:
{
"mcpServers": {
"yandex-eats": {
"command": "node",
"args": ["/absolute/path/to/yandex-eats-mcp/dist/index.js"],
"env": {
"YANDEX_EATS_CLIENT_ID": "...",
"YANDEX_EATS_CLIENT_SECRET": "...",
"YANDEX_EATS_PARTNER_NAME": "..."
}
}
}
}Related MCP server: yandex-tracker-mcp
Variable | Required | Description |
| yes | OAuth client id |
| yes | OAuth client secret |
| for several write tools | Sent as |
| no | Default |
| no | Default |
| no | If |
Credentials are never accepted as tool arguments. Access tokens are never returned to the agent.
Tool | Description |
| Credential / token cache status (no token value) |
| Force OAuth refresh |
| Order history (max 1000; 180 days) |
| Details by |
| High-demand places |
| Current blocks |
| Block places ( |
| Unblock places ( |
| Force menu / stop-list import |
| Validate courier pickup code |
| Reply to feedback (may need subscription) |
yandex-eats://docs/overview
yandex-eats://config/status
yandex_eats_investigate_order
yandex_eats_resync_menu
# Unit + MCP integration (mocked Vendor API, in-memory transport)
npm test
# E2E: spawn dist/index.js over stdio (builds first). Live API smoke only if
# YANDEX_EATS_LIVE_E2E=1 and real CLIENT_ID/SECRET are set.
npm run test:e2e
npm run test:allSuite | Path | Network |
Unit |
| mocked |
Integration |
| mocked Vendor API + real MCP protocol (in-memory) |
E2E stdio |
| dry-run MCP child process |
E2E live |
| real Yandex (opt-in) |
npm test && npm run build
npm pack --dry-run
npm publishRequires an npm account with publish rights for yandex-eats-mcp.
docs/YANDEX_EATS_API.md — API research
docs/MCP_SERVER_PLAN.md — implementation plan
MIT
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP Server for agents to onboard, pay, and provision services autonomously with InFlow
Hosted Amazon Seller and Vendor MCP server for Claude, ChatGPT, Cursor, Codex, Gemini, Copilot.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yasmanmesa/yandex-eats-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server