webmcp implementationmake your websiteAgent-ready.

WebMCP, short for Web Model Context Protocol, is a draft web standard from the W3C Web Machine Learning Community Group, led by engineers at Google and Microsoft. It lets a web page register a short list of typed, callable tools with the browser, so an AI agent working on that page can call them directly with structured inputs and get structured results back, instead of screenshotting the page, guessing which button does what and simulating clicks. The tools are ordinary JavaScript functions or HTML forms your site already has, wrapped so the browser can hand them to an agent.

MCP, the Model Context Protocol, connects an AI model to a server from the outside, over the network. WebMCP lives inside the visitor's browser tab, on your page, and is called by the agent the visitor brought with them, such as ChatGPT's built-in browser or Gemini in Chrome. Same idea of tools with schemas, completely different place. You do not need an MCP server, an API or a developer on call to use WebMCP.

Chrome from version 149 and Edge from version 150 support WebMCP through origin trials, which means a token on your site switches it on for real visitors. Clients that call tools today include the ChatGPT desktop app's built-in browser, Gemini in Chrome, Codex and Chrome's Model Context Tool Inspector. Firefox and Safari have not shipped it yet. Everything we build is progressive enhancement, so visitors on any other browser see your site exactly as they do now.

Yes, with a platform-specific approach for each. Shopify already registers ten tools on every storefront, so the job there is auditing and extending them. WordPress, Webflow and Squarespace take declarative tools on your existing forms plus a small script for anything richer. Wix depends on your plan and domain setup. Custom builds in Next.js, React or plain HTML give us the most room. Tell us your platform in the form and we will tell you exactly what is possible before you commit to anything.

No. WebMCP adds a layer for agents alongside the interface people already use. Your pages, forms and design stay exactly as they are. Where a tool fills in a form, the visitor still sees the fields populate and presses submit themselves, unless you decide a particular tool is safe to complete on its own.

Fixed prices by site type. Brochure and service sites start from £1,200. Content, booking and membership sites start from £2,400. Ecommerce, directories and marketplaces start from £4,800, because product search, filtering and structured data have to cover every template across thousands of pages. An optional care plan from £150 a month covers token renewals, spec changes and re-testing. Send us your URL and you will have a fixed quote within two working days.

Most brochure and content sites go live within one to two weeks of sign-off. Catalogue-scale sites take two to four weeks, because search, filtering and per-template structured data need proper testing under load. You get a timeline with your quote, and nothing changes for your visitors until you have watched every tool work.

Because WebMCP is still a draft standard, Chrome and Edge only enable it on sites that opt in. An origin trial token is a short string registered to your domain that switches the API on for your visitors. Tokens are time-limited, which is why our care plan renews them. Without a token, your tools only work for developers who have turned on a local flag, which is no use to a customer.

Done properly, yes it is safe. Tools run in the visitor's own session with the same authentication and validation your existing interface uses, so an agent can never do anything the visitor could not do themselves. We mark every write tool so agents ask for confirmation before spending, sending or changing anything, we never expose more data than a tool needs, and every description is checked against what the code really does before it ships.

It covers the part of AI search that traditional SEO cannot reach: action. Structured data and clean crawler access get you found and cited by ChatGPT, Perplexity and Google AI Overviews. WebMCP then lets the agent finish the job on your site, whether that is a booking, an enquiry or a purchase. We build the two together, so every engagement includes the schema markup and crawler checks answer engines need alongside the tools that let agents act.

Yes. Noel runs the WebMCP Academy on Skool, where the whole process is taught from first tool to origin trial, with worked examples for WordPress, Shopify, Webflow, Wix and custom builds. If you would rather build than buy, start there. If you would rather have it done, tested and handed over, use the form on this page.

Your website address, what it is built on, and access to the site or your developer once we have agreed the scope. We take it from there. There is no pre-work, nothing to install and nothing to prepare before we talk.