Menu

Individual skill

agent-ready-webmcp

0upvotes

Sub-skill de agent-ready-cloudflare: Implement WebMCP

skills/agent-ready-cloudflare/webmcp/SKILL.md

Read pinned source

Source commit ec4099f92fdeadcf1771c2a3f64efa4970733c89

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
133
Repository last updated
Nov 1, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Implement WebMCP

Expose site tools to AI agents via the browser using the
[WebMCP API](https://webmachinelearning.github.io/webmcp/)
([Chrome blog](https://developer.chrome.com/blog/webmcp-epp),
[declarative API](https://github.com/webmachinelearning/webmcp/blob/main/declarative-api-explainer.md)).

## Requirements

- Call `document.modelContext.registerTool()` for each tool you want to expose; it returns a Promise
- Each tool needs `name`, `description`, `inputSchema` (JSON Schema), and an `execute` callback
- Tools should expose your site's key actions (search, navigation, data retrieval)
- Pass an `AbortController` signal in the options to unregister tools when no longer needed
- For existing HTML forms, add `toolname` and `tooldescription` to the `<form>` and `toolparamdescription` to its inputs to expose them declaratively
- Older Chrome builds expose the API on `navigator.modelContext`; feature-detect `document.modelContext` first and fall back to it if needed
Back to top