WebMCP
Using SmoothDeploy tools from an AI agent running inside the browser
WebMCP lets an AI agent access SmoothDeploy tools when the agent is running inside the browser alongside the console — for example, in a browser extension or an embedded chat panel.
Unlike the MCP server (which requires OAuth and a separate network connection), WebMCP is available automatically on any page that the console serves. No setup or credentials are needed.
How it works
When the console page loads, it exposes a model context object on the page (document.modelContext). An in-page agent reads the manifest at /v1/webmcp/manifest to discover which tools are available, then calls them through the page rather than over the network.
The tools available via WebMCP are the same set as those exposed by the MCP server, filtered to what makes sense for the current page context.
When to use WebMCP vs. MCP
Use WebMCP when your agent runs inside the browser (extension, embedded chat). Use the MCP server when your agent runs in a terminal, IDE, or any environment outside the browser.