WebMCP

About WebMCP

WebMCP directory: browse sites that register browser-native MCP tools on the page (WebMCP / document.modelContext) — no separate remote server to install. AI-native browsers and agents discover and call those tools while you stay on the site. MCPBundles indexes public WebMCP surfaces with security signals and category filters alongside hosted remote MCP servers.

Need to host WebMCP on your own site? WebMCP hosting for brands

Browse WebMCP MCP servers at /?webmcp=1

Learn how MCP fits your stack — then come back here to browse and connect servers.

What is WebMCP?

How browser-native MCP works, who it is for, and how it differs from remote MCP servers.

Read guide

WebMCP vs MCP servers

When to expose tools in the browser versus hosting a remote MCP endpoint.

Read guide

Add WebMCP to your site

Implementation patterns for shipping WebMCP on a production web app.

Read guide

WebMCP security

Permission boundaries, user consent, and safe defaults for in-browser tools.

Read guide

Frequently Asked Questions

What is the WebMCP directory?

The WebMCP directory is the MCPBundles browse view of sites that register browser-native MCP tools via document.modelContext. Search and filter them here the same way you explore hosted remote MCP servers — then connect from Claude, Cursor, or MCPBundles Studio when a listing fits your workflow.

What is WebMCP?

WebMCP is MCP exposed in the browser: a site registers tools on the page (via document.modelContext) so an AI-native browser or agent can act on that page without a classic hosted MCP endpoint URL.

How is WebMCP different from a hosted remote MCP server?

Remote MCP servers run on a provider's infrastructure and connect over HTTP/SSE. WebMCP runs in the context of a live web page — the tools travel with the site, not with a separate server hostname.

Which browsers support WebMCP?

Support is growing among AI-native browsers and experimental Chromium builds that implement the Web Model Context API. Standard browsers without that API ignore the registration safely.

Why list WebMCP sites in the MCP directory?

MCPBundles indexes WebMCP registrations we can observe on the public web — same discovery, security signals, and category filters as hosted servers, so agents can find browser-native tools alongside remote MCP.

Add MCP servers to your AI tools

Browse the directory, pick a server, and connect from Claude, Cursor, ChatGPT, or VS Code — sign in once and credentials stay in your workspace.

MCPBundles publishes this directory to help you discover MCP servers and integrations. Product and company names identify third-party services (including nominative fair use of trademarks where applicable); those marks belong to their owners. MCPBundles is not affiliated with, sponsored by, or endorsed by listed services unless a listing says otherwise. We describe listings for discovery only—not as an offer to sell third-party services. Directory rules, including how to raise listing concerns, are in our Terms.
WebMCP directory — browser-native MCP surfaces | MCPBundles