When the Website Has Its Own MCP Tools — WebMCP in Local and Remote Browser
· 6 min read
Ask AI:
TL;DR
- Local Browser and Remote Browser now expose browser_list_webmcp_tools and browser_call_webmcp_tool — your agent navigates to a page, discovers tools registered on
document.modelContext, and calls them with JSON input. - MCPBundles dogfoods WebMCP on www.mcpbundles.com — the skills catalog registers
search_skills,get_skill, andget_connect_urlso a browser session can query the marketplace from inside the page, not by guessing DOM selectors. - Works in cloud Chrome (Remote Browser) and Desktop Chrome (Local Browser, WebMCP enabled by default) — same navigate → list → call workflow, no separate bridge extension.
Modern sites are not just HTML anymore. Some already publish structured tools the page understands — search the catalog, fetch an entity, return a connect link. WebMCP is how those tools show up to in-browser agents. Until now, MCPBundles browser automation was excellent at clicks, snapshots, and screenshots — but blind to page-native APIs. That gap is closed.