Connect WebMCP in Chrome
WebMCP in Chrome
Every page on pirateskills.com hands an agent working inside Chrome the public tools directly – no clicking around. Read-only, and always as a visitor.
- Chrome origin trial
- Read-only
- 3 tools
What a browser agent sees
| Tool | What it does |
|---|---|
search_knowledge | Search the Pirate Skills knowledge: the Growth Codex, the Builder Codex and Insights |
list_events | Upcoming Pirate Skills events, soonest first by date, with a link to each event page (a Forge session links the Forge page, where the seat is sold) and, for a signed-in person, whether they are registered |
get_offers | What Pirate Skills sells right now, with prices, read live (only what is on sale appears, and only what create_checkout sells): the Pirate Pass and the Forge Pass (monthly, prices before VAT, three-month minimum), which replace the Pirate Forge tiers (those are listed only until the passes are on sale), and a Captain on Deck session with Ben (the price is per session; up to 10 in one checkout) while it is on sale – each bought with create_checkout |
How it works
- A small script in every page registers the tools through
document.modelContext.registerTool()when the browser offers it. A browser without WebMCP does nothing – no request, no work. - Calls go to the HTTP API with
credentials: "omit", so an agent in the page never acts as the signed-in person. Tools about a person are not offered here. - Each call names itself
webmcpin thex-agent-clientheader.
Try it
In Chrome, open any page on pirateskills.com, then the DevTools console:
const tools = await document.modelContext.getTools();
tools.map((t) => t.name);
await document.modelContext.executeTool(
tools.find((t) => t.name === "list_events"),
{ limit: 2 }
);The Chrome pilot
pirateskills.com takes part in Chrome's WebMCP origin trial until 30 March 2027, so agents in Chrome get the tools without anyone switching on a flag. In other browsers the page works as always.