Vaanzari Commerce MCP
OfficialVaanzari Commerce MCP + WebMCP
Public connection guide for Vaanzari Commerce MCP and browser-native WebMCP reference implementation for agent-assisted saree shopping.
Live app
Remote MCP
Connect a compatible MCP client to https://vaanzari.com/mcp using Streamable HTTP. Repository metadata and examples remain available for that protocol:
Remote MCP and browser WebMCP are complementary: remote clients connect to Vaanzari service, while WebMCP exposes page-native tools inside supported browsers.
Start with the MCP/WebMCP quickstart to choose the integration surface that fits your client.
Browser WebMCP
Vaanzari registers six browser-native tools through document.modelContext.registerTool(...):
search-sareesget-sareecompare-sareesopen-sareeadd-saree-to-cartopen-cart
An agent can search, compare, navigate, and add an available public product to visible cart state. Human keeps final judgment, personal information, checkout, payment, and order confirmation.
Quick start
npm install
npm run devOpen http://localhost:5173. This standalone reference demo uses a small public-safe fixture snapshot of shopper-visible catalogue fields. No private API, credential, account, payment, or deployment dependency is required.
npm run typecheck
npm run lint
npm test
npm run build
npm run check:webmcp
npm run secret-scanBrowser verification
Open /webmcp-diagnostics in a WebMCP-capable browser. It reports secure context, document.modelContext, registerTool(), optional getTools(), expected names, missing names, and READY/NOT READY without reading browser storage or customer state.
For live testing, use ChatGPT Desktop Site Tools or Chrome 149+ with WebMCP enabled. Ask: “Find Banarasi sarees under ₹20,000”, compare matches, open one, add it to cart, then open cart. See browser verification. Safari fallback can show normal storefront behavior but is not WebMCP registration evidence.
Architecture
src/webmcp/register.ts is browser-tool centerpiece. It depends only on a PublicCatalogClient, browser navigation adapter, and browser cart adapter. src/demo/ supplies fixture data and React state for local reproduction. See architecture and tool reference.
Public/private boundary
Production Vaanzari commerce platform remains in separate private repository. This repository contains independently runnable browser-native WebMCP source, public-safe fixture adapter, demo UI, diagnostics, tests, and documentation.
It contains no production credentials, payment implementation, private backend code, customer data handling, administrative interfaces, infrastructure, deployment configuration, or database code. Security boundaries state deliberate limits.
Devpost archive
Challenge-period provenance and submission material remain available for historical context, not as repository's primary purpose: challenge work, provenance, and submission checklist.
License and trademarks
Software is Apache-2.0. Brand and product-photo rights are separate; see TRADEMARKS.md.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vaanzari/vaanzari-commerce-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server