yandex-eats-mcp
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-mcpshow 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.
yandex-eats-mcp
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.
Install / run
Cursor / Claude Desktop (recommended)
{
"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"].
Local development
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
Environment variables
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.
Tools
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) |
Resources
yandex-eats://docs/overviewyandex-eats://config/status
Prompts
yandex_eats_investigate_orderyandex_eats_resync_menu
Tests
# 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) |
Publish to npm
npm test && npm run build
npm pack --dry-run
npm publishRequires an npm account with publish rights for yandex-eats-mcp.
Docs
docs/YANDEX_EATS_API.md — API research
docs/MCP_SERVER_PLAN.md — implementation plan
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
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