In-depth architectural comparison of the Nahook MCP 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
Nahook MCP
Delivery · Local stdio
Quality: 48/100 (Fair) | Auth: other
Yandex Lavka MCP
Delivery · Local stdio
Quality: 53/100 (Good) | Auth: other
Verdict Summary: Choose Nahook MCP 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 Nahook 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 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.
Nahook MCP is categorized under Delivery and uses a local stdio subprocess. In contrast, Yandex Lavka MCP belongs to Delivery using local stdio subprocess. Select Nahook MCP when you need capabilities focused on delivery and Yandex Lavka MCP when you require tools for delivery.
"The official MCP server for the Nahook webhook platform — trigger webhooks, inspect deliveries, retry failures, and manage endpoints from your AI assistant."
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.