yandex-eda-mcp

Install

npx skillfoxx add mcp/yandex-eda-mcp

claude mcp add --transport stdio yandex-eda -- npx -y yandex-eda-mcp

{
  "mcpServers": {
    "yandex-eda": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-eda-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "yandex-eda": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-eda-mcp"
      ]
    }
  }
}

code --add-mcp '{"name":"yandex-eda","type":"stdio","command":"npx","args":["-y","yandex-eda-mcp"]}'

{
  "servers": {
    "yandex-eda": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "yandex-eda-mcp"
      ]
    }
  }
}

codex mcp add yandex-eda -- npx -y yandex-eda-mcp

[mcp_servers.yandex-eda]
command = "npx"
args = ["-y", "yandex-eda-mcp"]

{
  "mcpServers": {
    "yandex-eda": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-eda-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "yandex-eda": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-eda-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "yandex-eda": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-eda-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "yandex-eda": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-eda-mcp"
      ]
    }
  }
}

{
  "mcp": {
    "yandex-eda": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "yandex-eda-mcp"
      ]
    }
  }
}

{
  "context_servers": {
    "yandex-eda": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-eda-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "yandex-eda": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-eda-mcp"
      ]
    }
  }
}

claude mcp add -s user yandex-eda -- npx -y yandex-eda-mcp

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.

Example request

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

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.

MCP

Transport

stdio

Authentication

not required

Security check

• 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

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.

Related