WebMCP install code generator

A two-line install code for your site. Once it is in place, AI agents that open your site can read its overview, key links and guides through set tools. Nothing shows on screen, and your site’s design and content stay as they are.

A proposed web standard that lets a page tell AI agents “here is what you can find on this site, and how”. Instead of guessing from the screen, agents get the information the site gives them. The Pagegloss code registers three tools: read the site overview, find links and read a guide.

WebMCP is still a feature Chrome is trialling. It works in Chrome-based browsers with the feature turned on, with agents that can call the tools. In browsers without it, the code does nothing and your site is unaffected. Below is the environment Pagegloss has verified itself.

We do not promise visibility or rankings. The install code makes sure agents read accurate information once they open your site; it does not register your site with outside AI services.

Inside the <head> of your site’s HTML. Put it in the header shared by every page and the tools register on any page. Site builders usually call the setting something like “header code” or “custom code”; the name varies. If you cannot edit the HTML, send the code as it is to your developer or agency.

Paste the two lines wherever your platform lets you add code to the <head> of every page. WordPress: a header code plugin, or your theme’s header. Shopify: Online Store › Themes › Edit code › theme.liquid, just before </head>. Webflow: Site settings › Custom code › Head code. Wix: Settings › Custom code, placed in Head on all pages. Next.js: render both script elements as they are in the root layout’s <head>, not with next/script. Astro: add is:inline to both script tags, or insert the code with set:html, so Astro leaves it unchanged.

It does not change how your site looks. The settings travel inside the code, so nothing extra is downloaded for them, and one small script loads without blocking the page. If that script differs in any way from the one Pagegloss published, the browser will not run it.

After pasting the code, open the “Check install” tab in the result card and press “Check installation on the site”. It tells you whether your home page has this exact code or an older one. To see whether a visitor’s browser registered the tools, open “Checking tool registration in a browser” in the same tab.

No. The settings live inside the code, so after editing you replace the code on your site with the new one. To edit later, load your site address again and the settings on your site come back as they are.

What you write is kept only in this browser, one site at a time. On another device, load your site address to get the settings on your site, or use “Export” under Advanced and open the file with “Import”. The same works when you switch between sites.

Remove the two lines from your site. There is nothing to do in Pagegloss; pages that were already open stop when they are opened again.

Yes, and there is no sign-up. One configuration holds up to 100 links, 100 guides and 10 tools (256 KiB).

Not on Pagegloss servers. Loading an address reads your home page once, and the installation check only compares your site’s code. What you write stays in this browser, so export it before clearing browser data. We count visits and a few actions, such as copying the code, with Google Analytics, never your site address or what you write.

No. The registered tools are read-only and return only what you wrote here. They do not touch your site’s data or visitor information.

Nothing happens. The code only works on the site it names: when the address in the settings differs from the page address, no tools are registered. Only your site’s managers can put code on your site.