We run WebMCP on our own site

Technology

Monogram makes websites usable by AI agents, and monogram.io is where we run WebMCP. In Chrome builds that support it through Chrome's WebMCP origin trial, our blog search, newsletter signup and contact form register as tools, so an agent in the visitor's browser can search our writing or send us a project inquiry by calling a tool instead of guessing at the page.

WebMCP is a W3C Community Group draft, not the Model Context Protocol. A page declares tools in JavaScript, and an agent already running in that browser calls them, with no server or transport to set up. The spec can still change, so we treat it as an addition to a site that already works for agents without it. That underlying layer is what we built for Kasada.

Monogram logo

The difference

Where it sits, and what we ship

  1. The page's session is the agent's session

    A server side tool has to be granted access on its own: a token, a scope, an authorization step. A page side tool runs inside the session the user already has. That removes an integration problem and replaces it with a harder question about what an in-browser agent should be allowed to do.

  2. One content model, two kinds of reader

    Kasada's pages are assembled from structured content in Sanity, so the Markdown an agent reads and the page a person reads come from the same source rather than two. A machine readable layer maintained by hand is a layer that goes stale, and a stale one is worse than none.

  3. It is a draft, and we say so

    WebMCP is a W3C Community Group draft that Chrome exposes through an origin trial, and the spec can still change. On monogram.io the tools sit on our blog search, newsletter signup and contact form, so a visitor whose browser lacks WebMCP uses the same forms by hand.

Writing

What we have published on this

Featured article cover image
How to get your website agent-ready

What agents can use on monogram.io

In current Chrome builds with WebMCP, these tools register on the pages that hold the matching search box or form:

  • search_blog searches the Monogram blog and returns matching post titles and URLs. It is marked read only.
  • submit_newsletter_signup subscribes an email address to our newsletter, and only after the user has given one.
  • submit_contact_form sends us a project inquiry. Its description tells the agent to call it only after the user has given a real name, email, company, budget and project description, and never to invent values.

For agents that do not run in a browser, monogram.io also serves a read-only MCP server at /mcp, described at /.well-known/mcp.json. That one is server-side MCP, not WebMCP. Our agent-ready checklist shows how to check each piece.