blinkit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEADLESS | No | Set to 'true' to run browser in headless mode, 'false' to see the browser action |
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 |
|---|---|
| check_loginA | Check if the current session is logged in. Returns 'Logged In' or 'Not Logged In'. |
| set_locationA | Manually set the delivery location via search. Pass 'detect' to click 'Detect my location'. The flow should be: login -> set_location('detect') -> add items -> check_cart -> if address not same, use get_addresses and select_address. Do not use this tool to fix address after adding items. |
| loginA | Log in to Blinkit. Returns status or prompts for OTP (which will be sent to your phone). |
| enter_otpC | Enter the OTP received on your phone to complete authentication. |
| searchB | Search for a product on Blinkit. Returns a list of items with their IDs. |
| add_to_cartB | Add an item to the cart. Optional: specify quantity (default 1). |
| remove_from_cartC | Remove a specific quantity of an item from the cart. |
| check_cartA | Check the current cart products, total value, and the delivery address. If the delivery address is not the intended one, use get_addresses and select_address to change it. |
| checkoutA | Proceed to checkout (clicks Proceed / Pay button). DO NOT call this if you need to change the delivery address. To change address, use get_addresses and select_address BEFORE checkout! Do not use set_location to fix address here. |
| get_addressesA | Get the list of saved addresses. Use this and select_address to change address on the cart page, if the address in check_cart is incorrect. |
| select_addressB | Select a delivery address by its index. Only use this BEFORE checkout. |
| proceed_to_payA | Proceed to payment (clicks Proceed button again). Use after selecting address. |
| select_payment_methodA | Select a payment method. Automatically chooses Cash on Delivery if available. If not, it opens UPI and generates a QR code to be scanned by the customer. |
| pay_nowB | Click the 'Pay Now' button to complete the transaction. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool has a distinct purpose: login, location, cart operations, address management, checkout steps, and payment. No two tools overlap in functionality; even sequential checkout steps are clearly differentiated.
All tools follow a consistent verb_noun pattern (e.g., add_to_cart, check_cart, select_address). Exceptions like 'checkout' and 'login' are single verbs but fit naturally and do not break the pattern.
14 tools cover the full grocery delivery workflow from login to payment without unnecessary complexity. The number is appropriate for the domain.
The tool set covers the essential user flow: login, location, search, cart management, address change, checkout, and payment. Missing features like order history or cancellation are non-critical for core delivery; minor gap.