The MCP hub › WebMCP
WebMCP exposes a site's tools to in-browser AI agents through navigator.modelContext. Drop in one script tag and your pages become agent-callable. The same extraction also emits a server-side MCP endpoint, so you cover both protocols from one source.
<script src="https://wmcp.sh/webmcp/aHR0cHM6Ly93d3cuYWxsYmlyZHMuY29tL3Byb2R1Y3RzL21lbnMtd29vbC1ydW5uZXJz.js" defer></script>
wmcp.sh reads your page (JSON-LD, OpenAPI, Shopify, and more) and turns it into tools.
The same tools serve as a WebMCP shim for in-browser agents and a server-side MCP endpoint for Claude, Cursor, and Codex.
Reads are free and instant. Live actions flow through the metered, graded execute path with kill switch and audit.
Browser agents are arriving, and they look for tools on the page via navigator.modelContext. Sites that expose tools get used by those agents; sites that don't are invisible to them. This is the cheapest way to be on the right side of that shift, and it doubles as a server-side MCP endpoint.