WebMCP Hosting
Agent tools on your homepage — without exposing API keys in the browser
Browse WebMCP servers in MCPBundles
Compare indexed WebMCP sites in the open MCP directory — browser-native tool menus agents can discover on the public web.
Open the WebMCP directoryWebMCP in four parts
What the browser API does, where it stops, and why the credentials belong on a server you do not have to run.
What WebMCP is
WebMCP is a W3C-aligned browser API: pages register tools with document.modelContext so in-browser agents can search, quote, navigate, and click out to your checkout — on your origin, in Chrome Origin Trial today.
What WebMCP is not
It is not a replacement for remote MCP. ChatGPT Apps and Claude Connectors connect to mcp.yourbrand.com/mcp over the wire protocol — they never call document.modelContext on your marketing site.
Why the relay matters
Tool handlers should not embed upstream API keys in JavaScript. MCPBundles runs a tenant relay: the browser calls same-origin or MCPBundles-hosted endpoints; we hold credentials, rate limits, and audit server-side.
Discovery on your domain
Agents look for /.well-known/webmcp on your origin — a manifest listing tool names, descriptions, and schemas. We generate and host that manifest as part of WebMCP Hosting.
Shared relay — four steps
Most brands do not need two separate integrations. Wire data once through MCPBundles; choose www, mcp subdomain, or both.
- 1
Integrate once
CMS export, product feed, JSON-LD, sitemap-backed fetch, or web-app backend — we wire server-side tools through MCPBundles.
- 2
Surface on www
Hosted script + Origin Trial on www.yourbrand.com registers read/search/quote tools for Chrome browser agents.
- 3
Extend to mcp subdomain
The same relay powers MCP tools on mcp.yourbrand.com — carousel structuredContent for ChatGPT without standing up a new REST API first.
- 4
Directory sprint
Store submissions use mcp.yourbrand.com/mcp. WebMCP complements Shelf GEO; both share honest click-out to your site.
WebMCP vs remote MCP
Who calls it
- WebMCP (www)
- Chrome browser agents on your site
- Remote MCP (mcp subdomain)
- ChatGPT, Claude, Cursor, Hub, CLI
Where it lives
- WebMCP (www)
- www.yourbrand.com + /.well-known/webmcp
- Remote MCP (mcp subdomain)
- mcp.yourbrand.com/mcp + /docs
Protocol
- WebMCP (www)
- document.modelContext (browser)
- Remote MCP (mcp subdomain)
- MCP JSON-RPC (remote server)
Typical first step
- WebMCP (www)
- Homepage-only brands, CMS-led inventory
- Remote MCP (mcp subdomain)
- ChatGPT carousel + directory launch
Shared backend
- WebMCP (www)
- Yes — same MCPBundles relay
- Remote MCP (mcp subdomain)
- Yes — same MCPBundles relay
WebMCP questions
Do we need WebMCP to launch in ChatGPT?
No. ChatGPT needs remote MCP on mcp.yourbrand.com. WebMCP is an additional surface for Chrome browser agents on your marketing site. Many brands start with one relay and add both surfaces in the same engagement.
Can we add WebMCP if we only have a marketing site today?
Often yes — if we can build useful server-side tools from structured site content, CMS, or feeds. Pure static brochure copy with no inventory is still a weak fit for comparison-style carousels until we add a feed or backend.
Does MCPBundles use WebMCP on its own site?
Yes. mcpbundles.com makes directory search and selected product tools available through WebMCP. We use the same hosting architecture for customer sites.
How does this relate to Managed MCP Apps?
WebMCP Hosting is a spoke under our business offering. Managed MCP Apps is the full directory launch — build, docs portal, store submissions, and optional WebMCP on www. Request a scoping call and we map which surfaces fit your data path.
Ready to map www + mcp.yourbrand.com?
Tell us about your site, data sources, and directory goals. We reply within one business day with next steps.
Request a directory launch