blinkit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLINKIT_REQ_KEY | No | Override the auth_key / req_key constant if Blinkit rotates them. |
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": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| blinkit_login_statusA | Show whether a user is logged in and the saved location/store. |
| blinkit_send_otpA | Send a login OTP to a phone number (headless, no browser). Step 1 of login. |
| blinkit_verify_otpA | Verify the OTP and persist the access_token. Step 2 of login. NOTE: a wrong code returns ok:false even though Blinkit reports success. |
| blinkit_logoutA | Clear the stored access_token. |
| blinkit_set_locationB | Resolve a lat/lon, confirm serviceability, pick the express dark store, and save it as the default delivery location. |
| blinkit_check_serviceabilityA | Check if Blinkit delivers to a lat/lon (does not change the saved location). |
| blinkit_searchC | Search products. Returns clean product objects (id, name, brand, unit, price, mrp, inventory, eta) including the cart_item needed to add to cart. |
| blinkit_autosuggestC | Typeahead suggestions for a partial query. |
| blinkit_pick_bestA | Search and auto-pick the best product using the multi-factor scorer (brand + attributes + availability + price), with cheaper-equivalent swap. Returns the chosen product, alternatives, and the reason. |
| blinkit_recommendationsB | Products frequently bought with a given product id ('people also bought'). |
| blinkit_home_feedB | Products surfaced on the home feed for the saved location. |
| blinkit_add_to_cartA | Add line items to the working cart and reprice. Pass the product objects (or their cart_item) returned by blinkit_search/blinkit_pick_best. |
| blinkit_remove_from_cartB | Remove a product from the working cart by id and reprice. |
| blinkit_view_cartA | Show the working cart, repriced (items, payable amount, delivery, MROV). |
| blinkit_clear_cartB | Empty the working cart. |
| blinkit_quick_reorderA | Rebuild a basket from saved staples. With no keys, adds all auto-eligible staples silently; otherwise resolves the given staple keys. Returns the repriced cart and what was chosen for each item. |
| blinkit_list_staplesB | List the saved staple catalog and pick preferences. |
| blinkit_set_stapleC | Add or update a staple in the reorder catalog. |
| blinkit_get_addressesA | List saved delivery addresses (id, label, location). Requires login. |
| blinkit_checkoutA | Headless checkout prep: create a real server cart from items, bind the delivery address, and validate. Returns the server cart_id to pass to blinkit_prepare_order / blinkit_pay_upi. |
| blinkit_prepare_orderA | Mint a payment session for a server-synced cart (createOrder + zomato_payment_hash). Returns PAS token, orderId, payable amount. Fails if the order already has a pending payment. |
| blinkit_pay_upiA | Initiate UPI payment on a prepared order via Zomato zpaykit. method 'qr' returns a upi://pay intent link to open on the phone; method 'collect' attempts to push a collect request to the given VPA (PhonePe). Then poll status. |
| blinkit_payment_statusA | Check the status of the last (or a specific) in-flight UPI payment without re-initiating it. Returns pending / success / failed. |
| blinkit_order_countB | Lifetime order counts (delivered/live/cancelled). Requires login. |
| blinkit_order_historyA | Recent orders with totals, status, item names, and reorder product ids. Requires login. |
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 25 tools
Each tool targets a distinct action or resource (e.g., add_to_cart vs. remove_from_cart, search vs. pick_best). There is minimal overlap, and descriptions clearly differentiate similar tools.
All tools follow a consistent 'blinkit_verb_noun' pattern in snake_case, making the tool surface predictable and easy to navigate.
With 25 tools, the set is slightly larger than the ideal range but justifiable for a full-featured e-commerce MCP server covering login, location, cart, search, ordering, and payment.
The surface covers most lifecycle stages (login, search, cart, checkout, payment, staples), but lacks explicit order cancellation or address update during checkout, which are minor gaps.