Skip to main content
Glama

Blinkit MCP

Order groceries from Blinkit by talking to Claude (or any MCP client).

One sentence in, a filled Blinkit cart out

A real run against blinkit.com, sped up. Recorded on our scripted browser engine; on Browser Use (below) each step takes longer.

Claude sets your location, searches, fills the cart and shows you the bill. You pay yourself, through a live link to the browser. It never pays on its own.

Tools

Tool

What it does

blinkit_set_location

Set the delivery area

blinkit_search

Products with price, MRP, pack size and stock

blinkit_add_to_cart

Add an item by name or id

blinkit_view_cart

Items, bill breakdown, grand total, delivery time

blinkit_update_cart

Change a quantity, remove an item, or clear the cart

blinkit_login / blinkit_submit_otp

Log in with your phone number and OTP

blinkit_addresses

Your saved delivery addresses

blinkit_orders

Your recent orders

blinkit_checkout

The final bill plus a live browser link to pay in

blinkit_live_view

Watch or take over the browser

blinkit_status / blinkit_close

Session state; stop the browser

The browser profile is kept between runs, so you log in once. The cart carries over from one call to the next.

Related MCP server: Frisco MCP

Setup

Needs Node 20+ and a Browser Use Cloud API key (it runs the browser).

git clone https://github.com/vibhumaggarwal/blinkit-mcp
cd blinkit-mcp
npm install
cp .env.example .env    # paste your BROWSER_USE_API_KEY

Claude Code

claude mcp add blinkit -s user -- node "$PWD/server.mjs"

Claude Desktop, Cursor and others

{
  "mcpServers": {
    "blinkit": {
      "command": "node",
      "args": ["/absolute/path/to/blinkit-mcp/server.mjs"],
      "env": { "BROWSER_USE_API_KEY": "bu_..." }
    }
  }
}

Check it works:

node selftest.mjs          # protocol checks, free
node selftest.mjs --live   # a real location + search on Blinkit (uses Browser Use credits)

Good to know

  • Blinkit only delivers in India, and it blocks most data-centre traffic. Browser Use handles the browser side.

  • Logging in with a number Blinkit doesn't know creates an account. Use your own number.

  • Each step is a Browser Use agent task: roughly 20–80 seconds and a few cents.

  • State lives in ~/.blinkit-mcp (override with BLINKIT_MCP_HOME).

  • Unofficial. Not affiliated with Blinkit or Zomato.

Who made this

Built by the team behind Hunch, an AI friend you text on iMessage.

License

MIT

Available Tools

13 tools
blinkit_addressesSaved 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.

Inputs: no named parameters.

blinkit_add_to_cartAdd 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.

Inputs: items (required).

blinkit_checkoutCheckout (stops before paying)A

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.

Inputs: address.

blinkit_closeClose the browserA

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.

Inputs: no named parameters.

blinkit_live_viewLive browser linkA

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.

Inputs: no named parameters.

blinkit_loginLog in (send OTP)A

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.

Inputs: phone (required).

blinkit_ordersRecent 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.

Inputs: limit.

blinkit_set_locationSet delivery 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.

Inputs: location (required).

blinkit_statusBlinkit 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.

Inputs: no named parameters.

blinkit_submit_otpLog in (enter OTP)A

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.

Inputs: otp (required).

blinkit_update_cartChange cartA

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

Inputs: clear, changes.

blinkit_view_cartView 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.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to shop on frisco.pl, Poland's online grocery store, with secure manual authentication. Supports product search, cart management, and checkout preparation via browser automation without storing login credentials.
      10
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables assistants to search products, build and validate a Blinkit cart, manage delivery locations and addresses, and use saved staples or combos through Blinkit's JSON API while leaving payment to the user.
      MIT