How do I install WebMCP Demo Store?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does WebMCP Demo Store need an API key?

No required environment variable is listed on this record.

What transport does WebMCP Demo Store use?

WebMCP Demo Store is reached over HTTP.

When was WebMCP Demo Store last checked?

Last checked 2026-11-09. WebMCP demo store: same catalog via MCP tool calls vs DOM scraping. -79% bytes, -42% tokens.

WebMCP Demo Store MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://demowithmcp.converso.work/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http io.github.kamatanuj-webmcp-store https://demowithmcp.converso.work/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.kamatanuj-webmcp-store": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://demowithmcp.converso.work/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 1.0.0
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

WebMCP Demo Store — one-file server, two modes, one benchmark

Same store, same tools, two delivery modes:

WebMCP mode — the page exposes its catalog through MCP tool calls (MCP-over-HTTP /mcp, plus Chrome-native document.modelContext), so an agent reads only what the task needs.
Plain mode — the same store as an ordinary website; the agent parses full HTML pages, as every agent must today.

Benchmark (150-product catalog, identical tasks): 79% less action bytes, 42% fewer input tokens, 8/8 tasks correct in both modes. DOM mode wins on small catalogs then collapses; WebMCP wins with age. Crossover report: report.html → WebMCP_Comparison_Report.pdf.

Run it

python3 server.py                    # plain mode      → http://localhost:9501
MCP=1 PORT=9502 python3 server.py    # WebMCP mode     → http://localhost:9502 + /mcp

stdlib-only (http.server, json, uuid, threading) — no pip install, no dependencies.

Live demos

plain: https://demonomcp.converso.work
WebMCP: https://demowithmcp.converso.work (.well-known/mcp discovery, /mcp endpoint)
launch package (deck, whitepaper, reports): https://demowithmcp.converso.work/launch.html

Chrome-native WebMCP test (13 Oct 2026)

Chrome 154 + --enable-features=WebMCP exposes document.modelContext on HTTPS origins (about:blank excluded).

Registered the 5-tool store contract via the IMPERATIVE API (registerTool): search_products, add_to_cart, get_cart, checkout (server-backed; all fetches in-page).
Standard client flow verified: getTools() discovery → executeTool() calls → orders 1017/1018 placed, T2/T4/T8 picks correct (HP Pavilion 14, Razer DeathAdder, OnePlus 12R).
154 build quirks found & worked around:
1. executeTool(tool, args) requires args as a JSON string (object form throws "Failed to parse input arguments"); return values are JSON strings too — JSON.parse both sides.
2. Tools can't be re-registered under the same name (InvalidStateError) — reload the page to reset.
3. Flag/feature name: --enable-features=WebMCP works headless; docs' chrome://flags/#enable-webmcp-testing is the manual path. Note: API is document.modelContext (moved from navigator since July 2026 build).
Takeaway: the demo's tool contract is compatible with Chrome's native WebMCP, not just our JSON-RPC shim. When Chrome ships the client agent (Gemini-in-Chrome), the store is already agent-ready.

Repo layout

path	what
`server.py`	the whole thing: store + cart + orders + MCP transport (`MCP=1`) + static/report serving
`catalog.json` / `catalog_10.json`	150-product / 10-product demo catalogs
`compare.py`, `compare_llm.py`, `browser_llm.py`	benchmark harnesses (DOM-mode agent, LLM-token accounting, browser-native flow)
`make_report.py`	regenerates the HTML/PDF reports from `results.json` / `agg_150_vs_30.json`
`whitepaper.html`, `report.html`, `.pdf`, `chart_*.png`	strategy + evidence artifacts (launch deck included)
`weekly_recap.py`	counters + live-URL digest (used by the ops cron)

License

MIT.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install WebMCP Demo Store?

Does WebMCP Demo Store need an API key?

What transport does WebMCP Demo Store use?

When was WebMCP Demo Store last checked?

Documentation

WebMCP Demo Store — one-file server, two modes, one benchmark

Run it

Live demos

Chrome-native WebMCP test (13 Oct 2026)

Repo layout

License