Sharing my WebMCP build running on Vercel.
It’s an end-to-end setup: a provider surface (sirocco.gallery) exposing 5 callable tools, registered for Google’s Chrome WebMCP origin trial, plus a consumer extension on the Chrome Web Store that discovers and drives those tools with design-conformance awareness baked in.
I went with Vercel serverless for the backend because WebMCP tool calls are sporadic and stateless - functions spin up per call and match the security headers the origin trial requires, without babysitting a server.
Repo (consumer extension + architecture writeup): GitHub - sirocco-gallery/refraktor: A general-purpose WebMCP consumer: a Chrome side-panel agent that discovers and drives any page's registered tools through a Gemini chat. Companion to the sirocco.gallery reference implementation. Beta · GitHub
There aren’t many end-to-end examples out there yet, I’m learning as I go.