In-depth architectural comparison of the Yandex Lavka MCP and MCP Architect 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.
At a Glance & Executive Verdict
Yandex Lavka MCP
Delivery · Local stdio
Quality: 53/100 (Good) | Auth: other
MCP Architect
Delivery · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Yandex Lavka MCP if you need specialized Delivery tools running via a local process. Choose MCP Architect if your workspace requires Delivery integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
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.
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.
Gives any AI assistant real architectural understanding of a codebase: tech-stack overview, internal dependency graph with cycle detection, risk hotspots, and module summaries. Local, zero-config, no API keys. uvx mcp-architect.
Category & Scope
Tools & Capabilities Breakdown
Yandex Lavka MCP Tools (6)
Session and location management with saved addresses
Product search and detailed product info retrieval
Cart viewing, adding, updating, and clearing
Order preview without charge and confirmed order placement
3-D Secure payment handling with redirect support
Active order tracking and cancellation
MCP Architect Tools (5)
architecture_overview
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).
Yandex Lavka MCP is categorized under Delivery and uses a local stdio subprocess. In contrast, MCP Architect belongs to Delivery using local stdio subprocess. Select Yandex Lavka MCP when you need capabilities focused on delivery and MCP Architect when you require tools for delivery.