Answers before the sales call

No. Backend MCP makes persistent data and operations available outside the website, on your servers. WebMCP exposes frontend tools tied to an open browser tab, the current page and its session. They are designed to complement each other, and they do not share a wire format.

No. A WebMCP tool can call your existing APIs and application logic, but it does not replace the systems behind them. It is a declaration layer, not an architecture change.

Not yet. Browser and agent support is still developing: it is in origin trial in Chrome and Edge, with no signal yet from Firefox or Safari. We implement it as progressive enhancement and retain ordinary HTML and UI interaction as the fallback, so unsupported agents and every human visitor are unaffected.

Google has not identified WebMCP as a ranking signal, and we will not imply otherwise. Semantic improvements may help machines interpret a page more accurately, and that is worth doing on its own terms. Rankings are never guaranteed.

Usually not. The Retrofit is designed to enhance the existing site's semantics, controls and application logic. If we do recommend a design change, it will be because a specific journey cannot be completed without one, and we will show you the failing transcript.

Read-only tools can often run automatically. Purchases, messages, bookings, applications and private-data submissions should require visible user confirmation. The browser does not enforce that boundary, so we build it into the page and we test that it holds.

Whether agents can still understand the page, select the correct tools, complete important journeys, and stop at the required confirmation points. It also watches for structured-data regressions, claim drift and changes in browser support.