Doordash vs Yandex Lavka MCP

In-depth architectural comparison of the Doordash and Yandex Lavka MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Doordash when:

• You need dedicated capabilities in the Delivery domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Doordash Details

Choose Yandex Lavka MCP when:

• You need dedicated capabilities in the Delivery domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: other (Free / Open Source).
• You have access to required keys: YANDEX_LAVKA_MCP_TRANSPORT, YANDEX_LAVKA_MCP_CONFIG_JSON.
• Primary tools included: Session and location management with saved addresses, Product search and detailed product info retrieval, Cart viewing, adding, updating, and clearing.

Explore Yandex Lavka MCP Details

Feature & Specification Comparison

Specification	Doordash Delivery	Yandex Lavka MCP Dudude-bit Delivery
Summary	DoorDash MCP server — search, order, and track food delivery. By Strider Labs.	Order groceries from Yandex Lavka (Russia): search the catalog, build a cart, and place an order with a two-step confirmation before any charge. Unofficial (reverse-engineered private web API); local stdio or remote HTTP with OAuth. uvx yandex-lavka-mcp.
Category & Scope	Delivery

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "doordash": {
      "command": "npx",
      "args": [
        "-y",
        "directly"
      ]
    }
  }
}

{
  "mcpServers": {
    "dudude-bit-yandex-lavka-mcp": {
      "command": "uvx",
      "args": [
        "yandex-lavka-mcp"
      ],
      "env": {
        "YANDEX_LAVKA_MCP_TRANSPORT": "YOUR_YANDEX_LAVKA_MCP_TRANSPORT_HERE",
        "YANDEX_LAVKA_MCP_CONFIG_JSON": "YOUR_YANDEX_LAVKA_MCP_CONFIG_JSON_HERE"
      }
    }
  }
}

Related MCP Server Comparisons