Can My Agent Uselookup · compare · cite

Aug 28, 2026 · Catalog foundation is up

Specification feature · interfaces

WebMCP imperative toolsWebMCP draft 2026-08-26

Register JavaScript-backed tools through document.modelContext.registerTool().

Terminology basis: WebMCP draft 2026-08-26. WebMCP draft 2026-08-26

WebMCP imperative tools: 0 supported, 1 partial, 0 unsupported, 30 unreviewed across 31 cataloged products.

Markdown · JSON

Explore this familyMore in WebMCP6 capabilities

Current evidence by product

Can my agent use WebMCP imperative tools?

Read across for the answer. 1 of 31 current product columns have reviewed evidence; unreviewed does not mean unsupported.

Known issues (0)Report an issue
  • Supported0
  • Partial1
  • Unsupported0
  • Unknown30
  • Not applicable0

Web

9 products

Desktop

13 products

CLI

9 products

Unknown means no public evidence has been reviewed for that product and capability. It does not mean unsupported.

How statuses are assigned

Definition and scope

What this capability means

Register JavaScript-backed tools through document.modelContext.registerTool().

WebMCP is a draft Community Group Report, not a W3C Standard. Positive implementation cells must retain origin-trial, version, permissions, and agent-integration qualifiers.

Traceable compatibility

Assertion ledger

Documentation evidence only. No runtime conformance test is implied.

Chrome WebMCP origin trialdesktop · current
Partial
Target
Chrome WebMCP origin-trial documentation · dated-documentation
Environment
preview-enabled
Observed
2026-08-28
  • origin-trialregistration in the Chrome WebMCP origin trial is required
  • feature-flagsupport is not claimed for stable default Chrome
Evidence
  1. 1. Evidence checked 2026-08-28: Chrome documents this WebMCP behavior through its origin-trial developer surface; availability is experimental and must not be read as stable browser-wide support.