yandex-lavka-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lavka_statusA | Show whether the Lavka session and delivery location are configured. Read-only. Call this first to check setup before other tools. |
| set_locationA | Set the delivery location (required before catalog/cart calls). Provide either lat+lon coordinates or a saved address_id. Persists to config. |
| list_addressesA | List your saved Lavka delivery addresses (by name). Read-only. Use a returned |
| use_addressA | Switch delivery to one of your saved addresses, matched by name. Catalog, cart and prices are location-scoped, so this re-points everything. A saved address carries city/street/house; pass flat/entrance/comment if the order needs them. |
| set_delivery_address | Set delivery to ANY address by free text — works for a new city. Resolves the address to coordinates + city/street/house via Lavka's own geo search. Example: set_delivery_address("Казань, улица Баумана, 1", flat="12"). |
| search_productsA | Search the Lavka catalog at the current delivery location. Read-only. Each result has an |
| get_productA | Get details for one product: price, size, stock, description. Read-only. Pass the |
| view_cart | Show the current cart contents and running total. Read-only. The cart also reports order-readiness. Watch these:
|
| add_to_cart | Add a product to the cart (increments if already present). No charge.
IMPORTANT: search can return items that are only stocked in «Большая Лавка»
(a different store) — they add fine but can't be ordered from the current
one. After adding, check the returned cart's |
| update_cart_item | Set the exact quantity of a cart item. quantity=0 removes it. No charge. |
| clear_cart | Remove everything from the cart. No charge. |
| checkout_previewA | Preview the order: items, delivery fee, ETA, address, payment, TOTAL. Charges NOTHING. Show the returned total to the user and ask them to confirm it out loud before calling confirm_order. Always run this before confirming. If the summary has a |
| confirm_order | Place the order and CHARGE the card. Irreversible — real money. Call ONLY after checkout_preview was run and the user explicitly said yes to the previewed total. Pass that exact total as confirmed_total. The order is refused unless: a preview was run recently, confirmed_total matches it, and — critically — the live cart still matches the previewed cart at submit time (same version and total). If anything drifted, nothing is charged and you must preview + confirm again. Returns the order id and payment_status. "wait_user_action" means the bank requires 3-D Secure — give the user redirect_url to finish paying. cancel_order cancels. |
| cancel_order | Cancel an order by id (e.g. one returned by confirm_order/active_orders). |
| list_payment_methods | List the user's saved cards and which is the default. Read-only. Use a returned |
| set_payment_method | Choose which saved card orders will charge (persists). Pass an |
| active_orders | Currently tracked orders with status and ETA. Read-only. Covers in-progress orders (Lavka's order-tracking feed). Full historical order history is a separate endpoint not yet wired up. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Dudude-bit/yandex-lavka-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server