Architectural question related to WebMCP direction

[AL Meem]

Hello,

I recently joined the Chrome Built-in AI Early Preview Program and received the welcome message outlining the available resources and discussion channels. After reading through the materials and learning more about the WebMCP direction, it prompted a question about architectural compatibility.

While building my an agent-ready storefront, I ended up independently designing something conceptually similar to what WebMCP appears to be standardizing.

My current architecture includes:

• a deterministic context snapshot injected from the theme (productId, variantId, currency, locale) so agents don’t infer state from the DOM
• DOM contracts and custom events to make interactions machine-readable
• a governance layer for automated actions (confirm-before-write, audit logging, read-only default, kill-switch)
• an agent capability layer exposing structured skills for storefront analysis and guarded admin operations

So the storefront is already designed as an agent-readable interface, although it does not yet expose browser-native tools.

My question is:

From an architectural perspective, would a system like this be considered compatible with the direction WebMCP is proposing, or would adopting WebMCP require restructuring the interaction layer around browser-native tool registration (for example registerTool() or declarative form annotations)?

In other words, is WebMCP mainly a standardized exposure layer for agent-capable architectures, or does it assume a fundamentally different interaction model for web applications?

Thank you for your work on this it’s exciting to see the web moving toward more agent-native patterns.

Best regards,

[Sumeet Singh]

Hi AL Meem,

Thank you for your detailed question regarding the WebMCP architectural direction.

To help address your inquiry about compatibility, please find the [technical documentation/resource link] attached. This should provide more clarity on whether your current architecture, specifically your deterministic context snapshots and governance layer, aligns with the proposed browser-native tool registration models like registerTool().

Best regards,

Sumeet Singh

--
You received this message because you are subscribed to the Google Groups "Chrome Built-in AI Early Preview Program Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chrome-ai-dev-previe...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chrome-ai-dev-preview-discuss/CAPGf_8XfZ_XiopaQnn05TEp%2BWQG-gXGNB-54YB1D5S-aeVVyAg%40mail.gmail.com.