Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@quick-commerce-mcp Compare prices for Coke Zero across platforms"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Universal quick commerce aggregation via MCP - compare and order from Zepto, Swiggy Instamart, and BigBasket in one interface.
Multi-Platform Search: Find products across all platforms simultaneously
Price Comparison: See which app has the best deal
Smart Cart: Automatically suggest optimal platform split
User Control: You confirm before any order is placed
OTP Handling: Prompts for OTP when session expires
Related MCP server: blinkit-mcp
# Install dependencies
npm install
# Build
npm run build
# Configure MCP in Claude/Cursor
# Add to your MCP settings:
{
"mcpServers": {
"quick-commerce": {
"command": "node",
"args": ["/path/to/quick-commerce-mcp/dist/index.js"]
}
}
}Platform | Search | Cart | Order | Notes |
Zepto | ✅ | ✅ | ✅ | 10-min delivery |
Swiggy Instamart | ✅ | ✅ | ✅ | Good variety |
BigBasket | 🚧 | 🚧 | 🚧 | Coming in v1.1 |
"Find Coke Zero 6-pack"
"Where is milk cheapest right now?"
"Search for Maggi noodles on Zepto and Swiggy""Add to cart: 1L milk, 6 eggs, bread"
"Show me the best platform for these items""Compare prices for my cart"
"What's the cheapest way to get these items?"No payment info stored: We only automate cart building
OTP required: You'll always enter OTP manually
Confirm before order: Preview shown, you confirm final purchase
Session isolation: Each platform login is separate
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Claude │────▶│ MCP Server │────▶│ Playwright │
│ /Cursor │◀────│ (this repo) │◀────│ Automation │
└─────────────┘ └─────────────┘ └──────┬──────┘
│
┌─────────┐ ┌─────────┴──────────┐
│ SQLite │ │ │
│ Cache │ │ Zepto | Swiggy │
└─────────┘ └────────────────────┘Zepto automation
Swiggy Instamart
Price comparison
Basic cart management
BigBasket support
Scheduled reordering
Price alerts
Smart recommendations
Optimal split calculation
Order history tracking
This is a personal project. Open to suggestions!
This tool automates browser interactions for personal convenience. Use responsibly and in accordance with platform Terms of Service.
Created: 2026-02-12
Get current cart contents and total for specified platform.
| Name | Required | Description | Default |
|---|---|---|---|
| platform | Yes | Platform to get cart from |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must fully disclose behavior. It only says 'get', implying a read operation, but does not clarify whether the cart is user-specific or session-based, nor any potential side effects or limitations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence with no unnecessary words. It efficiently conveys the core purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the tool (one parameter, no output schema), the description adequately covers the basic purpose but lacks behavioral details that would fully inform an agent, such as how 'current' is defined or any authentication requirements.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage for the single parameter 'platform' with enum values. The description adds no extra meaning beyond the schema, so a baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('get'), the resource ('cart contents and total'), and the scope ('for specified platform'). It is specific and leaves no ambiguity about what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool, what prerequisites exist, or how it differs from alternatives. Since no sibling tools are listed, the absence of usage context reduces clarity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0get_cart_summaryScored across 1 tool
With only one tool, there is no risk of confusion between tools. The unique tool has a clear purpose.
The sole tool 'get_cart_summary' follows a clear verb_noun pattern, which is consistent and descriptive.
A single tool for a commerce server is far too few. Typical commerce operations require multiple tools (e.g., add/remove items, checkout), so this is an extreme mismatch.
The tool only retrieves cart summary, lacking any means to modify the cart, browse products, or complete purchases. This is severely incomplete for the stated domain.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Multi-tenant MCP gateway for AI commerce. One connection, every store.
Multi-tenant MCP gateway for AI commerce. One connection, every store.
Multi-tenant MCP gateway for AI commerce. One connection, every store.
Hosted MCP for e-commerce: live product catalog, stock, and pricing for AI agents.
