WebMCP vs. MCP: what runs in the browser, what runs elsewhere
A practical map of where browser-exposed WebMCP tools fit within the much broader Model Context Protocol ecosystem.
Read 7-minute guideWebMCP field manual
Original, source-linked guidance for deciding where WebMCP fits, designing narrow contracts, sharing state safely, and proving that the result works.
Status-sensitive claims reviewed Aug 31, 2026. WebMCP remains an experimental Community Group draft.
Start here
A practical map of where browser-exposed WebMCP tools fit within the much broader Model Context Protocol ecosystem.
Read 7-minute guideStart with the workflows, semantics, and verification signals your application already exposes before deciding which actions deserve tools.
Read 8-minute guideMake intent, inputs, side effects, and outcomes legible without persuasive, ambiguous, or overloaded prose.
Read 8-minute guideEvergreen library
11 of 11 resources
A practical map of where browser-exposed WebMCP tools fit within the much broader Model Context Protocol ecosystem.
Read resourceStart with the workflows, semantics, and verification signals your application already exposes before deciding which actions deserve tools.
Read resourceExpose one narrow action while keeping the visible interface, application services, and business rules intact.
Read resourceMake intent, inputs, side effects, and outcomes legible without persuasive, ambiguous, or overloaded prose.
Read resourceGive human controls and agent tools the same services, rules, state, and verification path.
Read resourceTreat tool registration as route- and component-owned state so stale tools never outlive the interface that gives them meaning.
Read resourceMeaningful evidence covers contracts, authorization, selection, state changes, and verified outcomes.
Read resourceReview WebMCP as another path into existing application behavior, with explicit attention to session privilege, misleading intent, excess data, and untrusted content.
Read resourceCompare equivalent completed journeys and publish the counting rules, evidence, and limitations behind the result.
Read resourceHistorical external-event coverage. isWebMCP did not participate in this challenge; these are not product release instructions.
Read resourceA dated, evidence-scoped harvest of 2,474 public project cards, 16 linked demo scans, and the product patterns worth carrying forward.
Read resourceQuestions, answered
Browser support, schemas, security, evidence, developer workflows, and the difference between MCP and WebMCP.
Browse all FAQsLatest signal
Commit 19fc565 clarifies observation context management in the experimental WebMCP draft. Implementers and conformance-test authors should review observation behavior against the updated draft; this is a specification clarification, not evidence of browser support or a W3C Standard release.