Browser-native MCP
WebMCP lets AI assistants use websites directly
A website can tell a supported AI assistant what actions are available on the page. The assistant can search, navigate, complete forms, or carry out other tasks without screen scraping.
Two ways sites expose MCP
Hosted remote MCP
A persistent HTTPS endpoint your client connects to — ideal for background agents, shared credentials, and always-on automations.
Remote MCP serversWebMCP
Tools registered on a live page — ideal for search, checkout, dashboards, and anything that should follow the user's session.
How WebMCP works
- Step 1
The website describes its actions
The page publishes a clear menu of supported actions and the information each one needs. - Step 2
The assistant discovers them
A compatible AI client reads that menu and understands what it can do on the current page. - Step 3
You remain in control
You ask for an outcome and approve sensitive steps while the site handles the action.
Use WebMCP on MCPBundles
The MCPBundles directory makes its search tools available through WebMCP. In a supported AI client, you can ask to find and compare MCP servers without leaving the conversation.
Common questions
- What is WebMCP?
- WebMCP lets a website describe the actions an AI assistant can take on the current page. A supported assistant can discover those actions and use them with the person's permission.
- How is WebMCP different from a hosted remote MCP server?
- Remote MCP servers run on a provider's infrastructure and connect over HTTP or SSE. WebMCP runs in the context of a live web page — the tools travel with the site, not with a separate server hostname.
- Where can I use WebMCP on MCPBundles?
- MCPBundles registers WebMCP tools on this site — including the public MCP directory — so supported AI clients can search and browse the same index from chat. You can also explore indexed WebMCP sites in the directory's WebMCP browse view.
- Which clients support WebMCP?
- Support is growing among AI-native browsers and chat apps that can open a site and call page-registered tools. Standard browsers without the Web Model Context API ignore the registration safely.