WebMCP Demo Store MCP server
Commit Oct 21, 2026Provides a product catalog through both standard HTML scraping and optimized MCP tool calls to reduce token usage and action bytes.
Also known as kamatanuj/webmcp, webmcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.0
- Last commit
- Oct 21, 2026
- License
- MIT
What is WebMCP Demo Store MCP?
WebMCP Demo Store provides a product catalog through both standard HTML scraping and optimized MCP tool calls to reduce token usage and action bytes.
Summary generated from the project's README
About WebMCP Demo Store MCP server
WebMCP Demo Store offers a dual-mode product catalog designed to test how AI agents interact with web content. Developers can run the server in plain mode, which requires agents to parse full HTML pages, or in WebMCP mode, which uses optimized tool calls to minimize token consumption and action bytes. This server is built using only the Python standard library, meaning it requires no external dependencies or pip installs to function.
Users can deploy the server locally by running the python script with or without the MCP environment variable. In WebMCP mode, the server provides a /mcp endpoint and supports Chrome-native document.modelContext discovery. This setup allows agents to interact directly with specific tools like search_products, add_to_cart, get_cart, and checkout. The system is designed to be compatible with both JSON-RPC shims and native browser implementations like the upcoming Gemini-in-Chrome integration.
What you can do with it
- 1Compare data efficiencyA developer can measure the difference in token usage between standard HTML scraping and optimized MCP tool calls.
- 2Test native browser integrationAn engineer can verify if a store is ready for Chrome's native WebMCP features using the document.modelContext API.
Written from the project's README. Every use case is checked against a quote from it.
How to install WebMCP Demo Store MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall WebMCP Demo Store MCP in Claude Code
$ claude mcp add --transport http webmcp https://demowithmcp.converso.work/mcpInstall WebMCP Demo Store MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"webmcp": {
"url": "https://demowithmcp.converso.work/mcp"
}
}
}Install WebMCP Demo Store MCP in VS Code
.vscode/mcp.json
{
"servers": {
"webmcp": {
"type": "http",
"url": "https://demowithmcp.converso.work/mcp"
}
}
}Install WebMCP Demo Store MCP in VS Code CLI
$ code --add-mcp '{"name":"webmcp","type":"http","url":"https://demowithmcp.converso.work/mcp"}'Install WebMCP Demo Store MCP in Codex
$ codex mcp add webmcp --url https://demowithmcp.converso.work/mcpInstall WebMCP Demo Store MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.webmcp] url = "https://demowithmcp.converso.work/mcp"
Install WebMCP Demo Store MCP in Gemini CLI
$ gemini mcp add -s user --transport http webmcp https://demowithmcp.converso.work/mcpInstall WebMCP Demo Store MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"webmcp": {
"url": "https://demowithmcp.converso.work/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablekamatanuj/webmcp is public and reachablegithub.com/kamatanuj/webmcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-21github.com/kamatanuj/webmcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 400 msPass
README
View on GitHubWebMCP 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-nativedocument.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/mcpdiscovery,/mcpendpoint) - 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:
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.- Tools can't be re-registered under the same name (InvalidStateError) — reload the page to reset.
- Flag/feature name:
--enable-features=WebMCPworks headless; docs'chrome://flags/#enable-webmcp-testingis the manual path. Note: API isdocument.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.
WebMCP Demo Store MCP questions
How do I add WebMCP Demo Store MCP to Claude Code?
Run claude mcp add --transport http webmcp https://demowithmcp.converso.work/mcp in your terminal. Add --scope user to make it available in every project.
How do I add WebMCP Demo Store MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How does WebMCP mode compare to plain DOM scraping?
WebMCP mode uses MCP tool calls to expose the catalog, resulting in 79% less action bytes and 42% fewer input tokens compared to parsing full HTML pages.
Does this server require any external dependencies?
No, it uses only the Python standard library including http.server, json, uuid, and threading.
How do I run the server in WebMCP mode?
You can enable WebMCP mode by setting the MCP environment variable to 1 and specifying a port when running the server script.