Marrow

WebMCP and browser agents: when an AI agent visits your website

Browser agents are AI agents that use a web browser for someone, reading pages and filling in forms the way a person would. WebMCP, from engineers at Google and Microsoft, lets your site give those agents proper tools to call instead, like starting a quote, so they don't have to guess their way through a form built for people.

  • WebMCP
  • browser agents
  • AI filling in forms
Where it works

Chrome and Edge are building it in, and ChatGPT's browser already uses it.

  • Chrome

    In an origin trial since Chrome 149 in June 2026, which sites can sign up to now, though Gemini in Chrome doesn't call the tools yet.

  • Edge

    In an origin trial since Edge 150 in July 2026, and Microsoft said in September that it's ready for sites to test.

  • ChatGPT

    The browser in ChatGPT's desktop app has called sites' WebMCP tools since August 2026.

  • Marrow

    Running on onmarrow.com today, and we're glad to show it to you or talk through your own site.

WebMCP is still being worked on in a W3C community group, so the details may change before it's final. The tools only start the journey, though, and that's the same one Marrow runs in every other channel.

How it works

What an agent does on your site, with and without WebMCP.

Without it, an agent fills in your form the way a person would.

They read the page, find the fields and type in what they think the customer meant. Anything they're unsure of gets guessed, and nothing records which answers were guesses.

What it enables

What it gets you when an agent turns up on your site.

Questions

What people ask us about WebMCP and browser agents.

What is WebMCP?

A proposed web standard from engineers at Google and Microsoft that lets a website offer tools an AI agent in the browser can call, like starting a quote, so it doesn't have to read and click its way through the page. It was first published in August 2025 and is being developed in a W3C community group.

Which browsers support it?

Chrome and Edge both have it in origin trials that sites can sign up to, though Chrome's own Gemini agent doesn't call the tools yet. The browser in ChatGPT's desktop app already calls WebMCP tools. Safari and Firefox don't support it yet (Apple has said it opposes it, and Mozilla is neutral), so the details may still change.

What do browser agents do with our forms today?

Fill them in the way a person would, from what they can read on the page. The main ones are designed to pause for the customer before submitting a form, signing in or paying, but neither the agent nor your form knows which answers were guesses.

Is it worth adding now?

It's early, but ChatGPT's browser already uses it, and every agent that calls your tools is one that isn't guessing its way through your form. Because the journey behind the tools lives in Marrow, a change to the standard means updating the tools, and the sale behind them stays as your compliance team signed it off.

Can we use WebMCP with Marrow?

We run it on onmarrow.com today, and the tools there start the same journey Marrow runs in ChatGPT and Claude. If you'd like to see it, or talk about putting it on your own site, get in touch.

Should we let browser agents onto the rest of our site?

We'd say yes, on your own terms. It's worth deciding which pages and actions they can reach, sending the ones that say who they are to tools like these, and keeping out the ones collecting prices with no customer behind them. That's work for your web and security teams rather than part of Marrow's product, but it's something we help clients plan.

Is there FCA guidance on browser agents?

Not specifically. The FCA-commissioned Mills Review in July 2026 called for the foundations of agentic finance, including mandates and auditability, and warned that an agent applying for a product arrives at a firm with no verified identity.

Get in touch

Talk to us about selling through AI agents.

We’d be glad to show you how it works with one of your own products.