SkillFoxx

yandex-eda-mcp

A Playwright-based MCP server for Yandex Eda: restaurant search, cart and order placement with dry-run protection against accidental payment

  • 4 ★ on the repository
  • Last commit
MCP server

Broad access

Why this level

  • Can place and pay for a real order with a real charge when confirm: true is passed
  • Stores the Yandex account login session in a local browser profile
  • Browser automation depends on a third-party site's layout and can break when it changes
All reasons and checks
Russian stack

sandexplus/yandex-eda-mcpAuthor:sandexplus

Install

Services

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/yandex-eda-mcp

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Can place and pay for a real order with a real charge when confirm: true is passed
  • Stores the Yandex account login session in a local browser profile
  • Browser automation depends on a third-party site's layout and can break when it changes

This is third-party code. Review the repository files before installing.

What it does

The server drives the Yandex Eda website with a headless Playwright browser in a persistent Chromium profile: login into the account happens once in a visible window, and every action after that runs headless. The tools cover the whole order flow: checking login status, picking a delivery address from saved ones or by map, searching restaurants, viewing menus, adding items to the cart, viewing the total, listing payment methods and placing the order. Ordering defaults to a dry-run mode: the server reaches the checkout button but does not click it, and an actual payment needs an explicit confirm: true parameter. Data is read primarily from the site's internal JSON API by intercepting network responses, which holds up better against layout changes than DOM selectors.

Who it is for. For people who want to delegate food ordering in their own Yandex Eda account to an agent.

Good fit when

  • You want to quickly build a cart and order food through a conversation with an agent
  • You want a saved delivery address without re-entering entrance and apartment details
  • You need protection against accidentally confirming an order: the server does not spend money by default

Not a fit when

  • You need unattended SBP payment: it requires confirmation in the banking app and the order is cancelled without payment
  • You need an official API instead of browser automation: the server emulates a user's actions on the site

Example request

Find a pizza place that delivers to my home address and build a cart for two, but do not place the order

MCP

Transport
stdio
Authentication
not required

Environment variables

YANDEX_EDA_HEADLESS
Show the browser instead of headless mode; headless is on by default
YANDEX_EDA_AUTO_LOGIN
Automatically open the login window when the profile is not authorized
YANDEX_EDA_DATA_DIR
Storage folder for the browser profile and screenshots, defaults to ~/.yandex-eda-mcp

Limitations

No license is declared in the repository. The author states plainly: the project automates your own account for personal use, you must follow Yandex Eda's terms, and responsibility for charges and orders made by the automation rests with the user. The server depends on the site's layout and internal API, and changes there may require fixing selectors in src/eda.ts. The first run downloads about 150 MB of Chromium.

How to disable. Remove the server from your MCP client config and delete the ~/.yandex-eda-mcp profile folder to sign out of the account.

FAQ

Can the agent accidentally place and pay for an order?

No, place_order defaults to dry-run and only reaches the checkout button; actually sending the order requires an explicit confirm: true parameter.

Why doesn't an SBP order complete automatically?

SBP payment requires manual confirmation in the banking app, so Yandex Eda creates and then cancels such an order without payment; automatic checkout needs a card instead.

Discussion

No questions or reviews yet.

MCP servers

MCP for Yandex Delivery

A1 Яндекс Доставка MCP

Russian stack

MCP server for Yandex Delivery B2B API: cost calculation, order placement, and tracking for same-day and next-day deliveries across Russia

MCP serverBroad access
Russian stack

Local MCP server for product search, cart and delivery with Pyaterochka

MCP serverBroad access4
Russian stack

A remote MCP server for htmlweb.ru with dozens of methods: INN checks, geodata, calendar, validators, plus card binding and charges

MCP serverBroad access
Russian stack

A TypeScript Yandex Tracker MCP server with boards, sprints and bulk issue operations

MCP serverBroad access
Russian stack

A CDEK API MCP server with a delivery calculator across all tariffs, courier booking and an HTTP mode for external agent platforms

MCP serverBroad access
Russian stack

A monorepo of MCP servers for Russian and CIS APIs: payments, CRM, marketplaces, delivery, HR and reference data

MCP serverBroad access38

README in short

The Russian README describes the server as a Playwright wrapper with a persistent Chromium profile stored outside the code. It gives a table of 13 tools, a detailed order scenario from address to payment, the saved-address mechanics, the dry-run ordering mode, and the SBP versus card payment quirk. It lists environment variables for headless mode, timeouts, data paths and the user agent. It separately explains that data is read from the site's internal JSON API for resilience against layout changes, and includes a disclaimer that the user is responsible for automating their own account.

README badge

Report a problem