· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Frédéric Barthelet v1.0.0
Add WebMCP tools to my website
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
add WebMCP tools to proxy my existing MCP server
Developer declarations; not independently tested. Listing last checked Nov 19, 2026. Package observed Nov 19, 2026.
From the marketplace listing
Guides an agent to inventory a web app, design non-overlapping page tools, register them via declarative, imperative and/or bridged implementation and dogfood them with Chrome DevTools MCP.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →---
name: webmcp
description: >-
Make a website usable by in-browser AI agents with WebMCP. Plan which paths
to expose, then ship them as declarative form annotations, dedicated
imperative tools, or a bridge to an existing MCP server. Use when the user
mentions WebMCP, document.modelContext, navigator.modelContext, registerTool,
webmcp-proxy, or browser agents.
---
# WebMCP — make a website agent-compatible
WebMCP lets a **page** register tools that in-browser AI agents can call. It is
**not** a remote MCP server and **not** an MCP App / ChatGPT widget.
Canonical surface: `document.modelContext.registerTool(...)`.
Fallback (deprecated): `navigator.modelContext`.
Declarative surface: HTML `<form>` attributes (`toolname`, `tooldescription`).
## When this skill applies
- User asks to make a site / app **WebMCP compatible**
- Mentions `document.modelContext`, `navigator.modelContext`, `registerTool`,
`webmcp-proxy`, or declarative form tools
- Wants browser agents to use page actions without DOM scraping
**Do not use this skill** for building remote MCP servers, ChatGPT/Claude MCP
Apps, or Skybridge UIs.
## Workflow (follow in order)
Copy and track:
```
WebMCP Progress:
- [ ] 1. Design: inventory + strategy + paths (stop for user agreement)
- [ ] 2. Wire runtime (native / polyfill) if the chosen strategy needs JS
- [ ] 3. Implement the agreed strategy (Declarative / Imperative / Bridge)
- [ ] 4. Dogfood with Chrome DevTools MCP
- [ ] 5. Harden (security, lifecycle, errors)
```
**Do not implement until step 1 is agreed.** Path choice is a product decision.
### 1. Design — UX paths worth exposing
Read [references/strategies.md](references/strategies.md) first.
Talk to the user. Propose; do not assume. Goal: a **short list of paths** and
**which strategy** ships each one.
1. Find the browser entry (HTML shell, `main.tsx`, router root) and stack
(vanilla / React-Next / Vue / other). If several apps exist, ask which one
first.
2. Inventory, then **ask**:
- What jobs should a browsing agent complete on this site?
- Are there existing HTML `<form>`s that should become tools as-is?
- Is there already a remote MCP server with the right tools/paths?
- Which human tunnels (checkout, onboarding, booking) should collapse into
one agent tool instead of step-by-step forms?
3. Present **Declarative vs Imperative vs Bridge** (mix OK; first ship should
stay small). Use the user’s domain in the examples.
**Declarative — expose existing forms as tools.** Add missing WebMCP meta on
existing form DOM (`toolname`, `tooldescription`, `toolparamdescription`,
optional `toolautosubmit`) so each form is a declarative tool. Fast, visual
(browser fills the form). See [references/declarative-forms.md](references/declarative-forms.md).
**Imperative — craft dedicated paths.** Unlike Declarative tools (via form),
`registerTool` packages a real agent path. Example: a 4-step checkout tunnel as
**one** tool from step 1 that fills everything and redirects to the last step.
Plan with the user: which scenarios, what **input**, what **UI/state outcome**.
See [references/tool-design.md](references/tool-design.md).
**Bridge — expose an existing MCP server.** Reuse the tools and paths already
designed for a shipped MCP server. `webmcp-proxy` is a fast first patch that
registers those tools on WebMCP for any AI browsing agent. It **lacks visual
feedback** in the browser. It **can leverage existing webapp credentials** if
the MCP server uses the **same OAuth client**. See
[references/proxy-existing-mcp.md](references/proxy-existing-mcp.md).
4. Write back a proposal and wait for a yes / edits:
```
Proposed WebMCP paths:
- [strategy] path — input → UI/state outcome
- …
Out of scope this round: …
```
5. Only then implement. If the user is unsure, recommend: **Bridge** if an MCP
server already exists; **Declarative** if the site is form-heavy;
**Imperative** for the one high-value tunnel they care about.
### 2. WirePreview of the first 4,000 characters. Read full instructions →
Referenced files: 8 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 19, 2026.
plugins_6a8ebee3dc2c819198e336f2a2ead981
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.