Claw Tsaver vs Yandex Lavka MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Claw Tsaver vs Yandex Lavka MCP
In-depth architectural comparison of the Claw Tsaver 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.
At a Glance & Executive Verdict
Claw Tsaver
Delivery · Local stdio
Quality: 41/100 (Fair) | Auth: No auth required
Yandex Lavka MCP
Delivery · Local stdio
Quality: 53/100 (Good) | Auth: other
Verdict Summary: Choose Claw Tsaver if you need specialized Delivery tools running via a local process. Choose Yandex Lavka MCP 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 Claw Tsaver 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).
Primary tools included: Configurable token threshold, SQLite storage for oversized responses, Preview and on-demand expansion handles.
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.
Token-saving MCP proxy that intercepts oversized tool returns and replaces them with a preview + on-demand handle. Real benchmark: 11,507 tokens → 104 tokens (99.1% saved) on a Wikipedia fetch. Works with OpenClaw + Claude.
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
Tools & Capabilities Breakdown
Claw Tsaver Tools (5)
Configurable token threshold
SQLite storage for oversized responses
Preview and on-demand expansion handles
Downstream MCP server forwarding
Optional local savings dashboard
Yandex Lavka MCP Tools (6)
Session and location management with saved addresses
Product search and detailed product info retrieval
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).
Claw Tsaver is categorized under Delivery and uses a local stdio subprocess. In contrast, Yandex Lavka MCP belongs to Delivery using local stdio subprocess. Select Claw Tsaver when you need capabilities focused on delivery and Yandex Lavka MCP when you require tools for delivery.