docs: Document browser WebMCP support

[rgarcia]

Summary

Document browser WebMCP support beyond the changelog so developers can discover and invoke page tools safely.

• Add a browser guide covering registration, discovery, tab/frame provenance, reference lifecycle, invocation limits, terminal statuses, unknown outcomes, and untrusted page data. Include TypeScript, Python, Go, and curl examples.
• Document the browser-wide Playwright helpers and add a dedicated MCP webmcp tool page, following the existing per-tool reference structure. Link it from the MCP overview and add both new pages to navigation.
• Keep tool selection examples name-only and document workload-specific execution timeouts: 5 seconds for reads, 10 seconds for navigation or quick tool calls, and longer budgets for slower work. The WebMCP helper example uses a 5-second tool timeout inside a 10-second execution budget.
• Link the existing generated API reference. Both endpoints are present in the live OpenAPI spec configured by docs.json; no hand-written endpoint reference pages or generated files are needed.

Verified API fields, browser defaults, helper behavior, MCP guidance, and SDK signatures against source, including all three SDKs' v0.100.0 api.md files. Document that HTTP 200 can return canceled or error, and disable SDK retries in invocation examples to avoid repeating side effects after a lost response or 504.

Validation

• mint broken-links and mint validate pass.
• mint dev --no-open: all five affected content pages load locally; checked rendered WebMCP content.
• TypeScript samples type-check against @onkernel/sdk@0.100.0. Python samples execute against kernel==0.100.0. Go discovery and wrapped invocation samples are formatted with gofmt and compile against kernel-go-sdk@v0.100.0.
• Temporary mock-server checks exercise all three SDK examples for completed, canceled, error, 504, empty-list, and missing-tool cases. Confirm exactly one invocation after 504 and no invocation when the requested tool is absent. Curl discovery/invocation and TypeScript/Python Playwright request shapes also pass.
• Execute both embedded helper examples against the helper implementation with mocked responses: completion, empty discovery, frozen helper object, and the exact outcome_unknown error message pass.

No live browser invocation was performed. Examples require an existing browser and a site's verified tool schema, and assume a single search_products registration. The provenance section explains how to distinguish duplicate names when needed.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
Kernel	🟢 Ready	View Preview	Sep 8, 2026, 3:26 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[cursor]

Stale comment

Risk assessment: Very Low

Decision: Approval stands (already approved; risk did not increase)

Re-evaluated after the new commit (9324e3f) on this previously approved PR. The update is still documentation-only. Risk remains Very Low; approval is not revoked and is not re-issued.

Evidence from the diff

• 6 files, +406 / -11 vs main: new browsers/webmcp.mdx and reference/mcp-server/tools/webmcp.mdx; edits to browsers/playwright-execution.mdx, reference/mcp-server.mdx, reference/mcp-server/tools/execute-playwright-code.mdx, and docs.json
• Incremental change since the prior approval: example copy and sample timeouts (e.g. 60s/120s → 5s/10s), plus simpler name-only tool selection in samples. Same file set; no new paths
• Changed paths are Mintlify MDX and two sidebar entries in docs.json only — no application code, CI, auth, infra, or schema changes
• No CODEOWNERS file in this repo

Risk factors

• Codepaths / blast radius: public docs site content and navigation only
• Infra / ops / security: none; no production logic in this repository
• Complexity: new product docs and examples, not executable behavior change here

These files are product documentation, not model instruction or prompt files.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Risk assessment: Very Low

Decision: Approval stands (already approved; risk did not increase)

Re-evaluated after the new commit (7512be7) on this previously approved PR. The update is still documentation-only. Risk remains Very Low; approval is not revoked and is not re-issued.

Evidence from the diff

• 6 files, +406 / -11 vs main: new browsers/webmcp.mdx and reference/mcp-server/tools/webmcp.mdx; edits to browsers/playwright-execution.mdx, reference/mcp-server.mdx, reference/mcp-server/tools/execute-playwright-code.mdx, and docs.json
• Incremental change since the last assessment: two wording edits (your site → the site) in existing MDX copy. Same file set; no new paths
• Changed paths are Mintlify MDX and two sidebar entries in docs.json only — no application code, CI, auth, infra, or schema changes
• No CODEOWNERS file in this repo

Risk factors

• Codepaths / blast radius: public docs site content and navigation only
• Infra / ops / security: none; no production logic in this repository
• Complexity: new product docs and examples, not executable behavior change here

These files are product documentation, not model instruction or prompt files.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[AnnaXWang]

qq - was the omission of awaiting_submission intentional?

this PR currently documents only completed, canceled, and error statuses,
the browser runtime returns this status for non-autosubmit declarative forms after populating the fields but before submission.

if awaiting_submission is meant to be publicly supported, we add it before merging. Non-blocking for now.

• add it to the public OpenAPI schema and regenerate/release the SDKs
• document that the form was populated but not submitted
• explain the next step: inspect the form, obtain any required confirmation, then submit through Playwright or computer interaction without invoking the tool again
  update the guide, Playwright helper page, MCP reference, and examples to handle all four statuses
• change the minimum SDK versions to releases containing the corrected enum
• add coverage for this response through the public API and documented client paths