WebMCP Development. A website agents can use.
We make websites usable by AI agents: WebMCP tools for the actions you choose, clean forms and structured data, and confirmation before anything is submitted or paid.
We grow your business with
- CROturn traffic into leads
- SEOrank & get found
- GEOwin generative search
- AEOget cited by AI answers
- AIbuild a website that learns
What WebMCP is
Get your website ready for AI agents
AI agents are starting to use websites the way people do: searching, filling in forms, booking and buying. WebMCP is a proposed browser feature that lets your site tell an agent which actions it offers, such as "search products" or "request a quote", instead of leaving the agent to guess from the page.
Be clear on where it stands. As of 6 November 2026 the WebMCP spec is a Draft Community Group Report of the W3C Web Machine Learning Community Group, not a W3C standard. The project's implementation status lists an origin trial in Chrome 149 and Edge 150; Firefox and Safari have not implemented it, and WebKit's standards position is to oppose it.
So we treat WebMCP as one part of making a site agent-ready, not the whole job. Read what WebMCP is, WebMCP vs MCP and how to add WebMCP to a website for the detail.
What we do
WebMCP and agent-ready website services
Agent-readiness review
Which jobs an agent would try on your site, where it would get stuck, and what to expose first.
WebMCP tools
The actions you choose, registered with the browser API in the current WebMCP spec, behind your existing sign-in.
Clean forms and markup
Labelled forms, clear buttons and structured data, which help agents and assistive technology on every browser.
Consent and safety
Read actions first, confirmation before anything is submitted or paid, and nothing exposed that a visitor couldn't do.
MCP server option
When agents need your data outside the browser, a remote MCP server or ChatGPT app may fit better.
Updates as the spec moves
WebMCP is still changing. We track the spec and browser support and update your tools when it changes.
How we work
The guardrails on every agent-ready site
- Only actions a visitor can already take
- Read-only tools first
- Confirmation before submit, book or pay
- Your existing sign-in and permissions
- Feature detection, so other browsers are unaffected
- Code matched to the current spec
- Accessible forms that help every visitor
- Tested in the browsers that support it
- Everything in git, reviewed by an engineer
Because WebMCP is in an origin trial, we can't promise which browsers or agents will use it, or when. We'll tell you plainly if it isn't worth doing for your site yet.
The process
How a WebMCP project runs
Small, reversible steps, with a person signing off at each one.
Review
We map the jobs visitors and agents try on your site and pick two or three to expose.
Design the tools
Names, inputs, outputs and confirmations, written down before code.
Build
Tools added to your site behind feature detection, with forms and markup cleaned up.
Test
Tested in browsers with WebMCP support and checked that nothing changes elsewhere.
Monitor
We watch the spec and browser support and update your tools as they change.
Pricing
Quoted per project
WebMCP work is quoted as a fixed scope after a short call. The price depends on the number of actions, sign-in and how your site is built. It often fits into a redesign or ongoing site care.
Ask for a quote →Read first
Guides to WebMCP and agent protocols
What WebMCP is, how it compares with MCP and the other agent protocols.
What Is WebMCP? How Websites Expose Tools to AI Agents in the Browser
WebMCP explained in plain English: who proposed it, how pages register tools for AI agents, its draft status and which browsers support it as of November 2026.
Read the guide →WebMCP vs MCP: Browser Page Tools vs MCP Servers, and When You Need Each
WebMCP vs MCP compared for website owners: where each runs, who supports it, status as of November 2026, and when a site needs one, the other or both.
Read the guide →How to Add WebMCP to Your Website: Tools, Security and Testing (2026)
What adding WebMCP to a website involves in November 2026: the registerTool API from the official explainer, what to expose, consent and security, and testing.
Read the guide →AI Agent Protocols Compared: MCP, A2A, WebMCP, UCP, ACP and AP2 (2026)
MCP, A2A, WebMCP, UCP, ACP and AP2 compared in one table: what each connects, who runs it, status as of November 2026 and which businesses need each one.
Read the guide →
Project Managers who will work with you on your project!
Irina S.hello@eseospace.com
Benjamin G.ben@eseospace.com
David G.david@eseospace.comWork with us
Talk to the team behind your project
Tell us what you need and we’ll match you with the right people.
Book a Discovery Call
Jeanette M.jeanette@eseospace.com
Mark S.mark@eseospace.com
Maryna P.maryna@eseospace.com
FAQ
Common questions
Is WebMCP a web standard?
Which browsers support WebMCP?
Will WebMCP break my site in other browsers?
What is the difference between WebMCP and MCP?
Should I wait?
Want your website ready for AI agents?
Request a free AI and MCP readiness assessment, or book a call. We'll tell you which actions to expose, what to fix first and whether WebMCP is worth it for your site yet.
Request a Free Assessment →
