Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BLINKIT_MCP_HOMENoOverride the directory where state is stored (default is ~/.blinkit-mcp).
BROWSER_USE_API_KEYYesYour Browser Use Cloud API key, used to run the browser.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
blinkit_statusA

Whether the Blinkit browser is logged in, the delivery location it is set to, the delivery time shown, and how many items are in the cart. Starts the browser if it isn't running.

blinkit_set_locationA

Sets where Blinkit delivers to, by area, address or pincode (e.g. 'Indiranagar, Bengaluru'). Prices, stock and delivery time depend on it, so set it before searching. It picks Blinkit's best match and lists the other matches.

blinkit_searchA

Searches Blinkit for a product and returns results with id, pack size, price, MRP and stock, at the current delivery location.

blinkit_add_to_cartA

Adds items to the Blinkit cart. Name each item as exactly as you can (brand, variant, pack size) and pass the id from blinkit_search when you have it. Returns what was added, what wasn't and why (with the closest matches), and the cart with its bill.

blinkit_view_cartB

The Blinkit cart: items, quantities, and the bill row by row (items total, delivery, handling, any surge or small-cart fee) with the grand total.

blinkit_update_cartA

Changes quantities in the Blinkit cart, removes items, or empties it. Quantity 0 removes an item.

blinkit_loginA

Starts a Blinkit login with a mobile number: Blinkit texts that number a one-time code. Follow with blinkit_submit_otp. Only needed once; the login is remembered. Blinkit signs up a number it doesn't know, under its terms, so use this only for the number's owner at their request.

blinkit_submit_otpA

Finishes the login started by blinkit_login, with the one-time code Blinkit texted. Call it soon after: the code and the page both expire.

blinkit_addressesB

The delivery addresses saved on the logged-in Blinkit account, and which one is selected. Done by the engine's agent, so it needs a model on hunch-browser.

blinkit_checkoutA

Readies the cart for payment and stops: it never pays. Returns the bill and a live link to the browser where the person reviews the address and pays themselves. Needs a logged-in account with items in the cart.

blinkit_ordersB

The logged-in account's recent Blinkit orders: when, what, how much, and status. Done by the engine's agent, so it needs a model on hunch-browser.

blinkit_live_viewA

A link that shows the Blinkit browser live and lets the person take over: to pay, to solve something, or just to watch. Starts the browser if it isn't running.

blinkit_closeA

Stops the Blinkit browser session (it stops by itself after 10 idle minutes). The login is kept; the next tool call starts a new browser.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 13 tools

Disambiguation4/5

Most tools are clearly distinct by resource and action: search, add_to_cart, view_cart, update_cart, checkout, orders, etc. The main possible confusion is between blinkit_set_location and blinkit_addresses, though their descriptions make the difference clear enough. blinkit_status and blinkit_live_view also both interact with the browser session, but they serve different purposes.

Naming Consistency4/5

All tools use a consistent blinkit_ prefix and snake_case, which makes the set predictable and readable. The only minor inconsistency is that some names are noun-like or state-like (addresses, orders, checkout, status) rather than strict verb_noun patterns.

Tool Count5/5

Thirteen tools is well-scoped for a grocery-ordering workflow spanning login, location, search, cart, checkout, orders, and session control. Each tool appears to earn its place without obvious duplication or excessive surface area.

Completeness4/5

The surface covers the main shopping lifecycle: authentication, delivery location, product search, cart management, checkout handoff, order history, live takeover, and session close. Gaps are minor—such as no explicit saved-address management or product-detail endpoint—but core workflows are covered.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues