WebMCP ACME — Landing Page Agent-Ready
qiun/webmcp-acme
Landing page WebMCP-ready com formulários declarativos para agentes de IA
Ver no GitHubDemo de landing page para a empresa fictícia ACME construída com Vite + React + TypeScript que funciona tanto para humanos quanto para agentes de IA via WebMCP. Exemplifica a API Declarativa (formulário de contato como ferramenta) e ferramentas read-only leves, servindo como alvo realista end-to-end para testar agentes de browser.
Instalação
npx convez-ai qiun/webmcp-acme1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Testar agentes de IA em sites reais com WebMCP
- Demonstrar operações end-to-end de agentes (leitura de info + submissão de forms)
- Validar implementações do padrão WebMCP em casos de uso práticos
Veredito

Projeto de referência bem-executado para testar agentes de IA em ambientes realistas com WebMCP. Código limpo e bem documentado, mas é um demo específico — não uma ferramenta genérica para reutilizar diretamente em produção sem adaptações.
README
A tradução para o português deste README ainda está na fila.
webmcp-acme
▶ Live demo: https://webmcp-acme.vercel.app
A landing page for the fictional company ACME — it works normally for humans and responds to AI agents via WebMCP. The simplest of the four playground projects: it showcases the Declarative API (a contact form as a tool without JS) plus lightweight read-only tools.
Why this exists
This is one of four open demo sites built specifically to be agent-ready via WebMCP. We publish them so that anyone building AI browser agents — or working on the WebMCP standard and the MCP-B polyfill itself — has realistic, end-to-end targets to test against, not toy pages. Every user journey here (browse company info, read the offer, submit a contact form) can be completed by a human in the UI and driven entirely by an AI agent through WebMCP tools, with human-in-the-loop confirmation where it matters.
The goal is simple: make it easy to verify that an agent can really operate a WebMCP-enabled site, end to end. Fork it, point your agent at it, and see what works.
WebMCP demo set — live demos (source): acme · shop · stays · airline
Stack
- Vite + React 18 + TypeScript (
strict) - Tailwind CSS,
lucide-react zod(lightweight validation), the MCP-B polyfill (@mcp-b/global)- No backend — data lives in
src/data/company.ts, and the submitted form is a mock (log + toast).
Getting started
pnpm install
pnpm dev # http://localhost:5173
pnpm build # production
pnpm lint # ESLint (react-hooks + jsx-a11y)
pnpm typecheck # TypeScript strict
WebMCP tools
| Tool | Type | Description |
|---|---|---|
get_company_info | read-only | Company description, mission, location |
list_products | read-only | List of products with "from" prices |
get_contact_info | read-only | Phone, email, address, hours |
submit_contact_form | declarative | Contact form (toolautosubmit="false" → a human submits) |
The first three are registered imperatively in src/App.tsx via useWebMcpTool.
submit_contact_form is created declaratively — from HTML attributes on the <form> in
src/components/ContactForm.tsx, with no registering code.
How to test with an agent
- Native Chrome 146+ with the WebMCP flag (
chrome://flags) — the agent reads the read-only tools and can fill in the (declarative) form. - MCP-B polyfill (loaded automatically by
src/lib/webmcp.ts) + the@mcp-b/webmcp-local-relaybridge → connect Hermes / OpenClaw / your own MCP agent. - Scenarios: "What does ACME sell?" →
list_products; "What's the phone number?" →get_contact_info; "Send a message asking about ACME Drive X" → the agent fills insubmit_contact_formand waits for a human to click.
The visible Declarative API states (:tool-form-active, :tool-submit-active) are in src/index.css.
API stability (June 2026)
WebMCP is a W3C Community Group Draft Report — not a standard. Imperative surface:
document.modelContext.registerTool/unregisterTool (navigator.modelContext deprecated since
Chrome 150). Declarative surface: the toolname, tooldescription, toolparamdescription,
toolautosubmit attributes on <form>. When the imperative API changes → you fix only
src/lib/webmcp.ts. Changelog: developer.chrome.com/docs/ai/webmcp.
Deploy
Vercel / Netlify / GitHub Pages. HTTPS required (WebMCP works only in a secure context).
Set Content-Type: application/json for /.well-known/webmcp.
License
MIT — see LICENSE.