WebMCP: how websites are becoming agent ready

What does an agent-friendly website actually look like? A recent episode of The Startup Ideas Podcast walked through WebMCP, and it's the clearest answer so far. Here's the summary, written for people who build or run websites, not for protocol nerds.

So what is WebMCP?

WebMCP is the Model Context Protocol, brought inside the browser interface. Microsoft and Google worked on it together, and it landed in Chrome as an experimental feature in February. Your site publishes a short list of tools. Whatever agent the visitor already uses, whether that's Claude, ChatGPT or something else, reads that list and calls the tools it needs.

The old way was much heavier. An agent would pull the whole page structure, scan the code, take screenshots and hunt for the right button. That's slow, and it breaks the moment you ship a redesign.

The demo that makes it all click

The example was an espresso store. The shopper typed a plain request: upgrade my machine so I can make two flat whites a day, with about 32 centimetres of counter space. The page responded on its own, put two machines side by side and highlighted the exact specifications behind the request.

Then the shopper asked which accessories fit one of the machines. The store exposed tools for reading the customer's existing gear, reading the cart and applying coupons. The agent suggested a matching water softener, added it to the cart when asked and applied a ten percent discount. The whole time, the normal shopping interface stayed right there on screen.

The clever part is the login

API keys, tokens and identity plumbing are what stop most stores from going agent friendly. WebMCP sidesteps all of that by running on the browser session. The visitor logs in with a normal username and password, and the agent simply inherits that session as it is.

It also means the tool list can change depending on who's there. Logged out visitors might see three tools. Logged in visitors get the full set. It's the least technical route to an agent-ready store, and it still comes with the most features.

Where WebMCP fits on the spectrum

Raw API: headless, and the agent has to have a key.

MCP server: headless, and one more layer to run on your backend.

Computer use: the agent takes screenshots and clicks around like a person would. Slow.

Browser MCP: the agent reads the page markup and has to guess where to click. Fragile.

WebMCP: the site hands over a tool list, and the visual interface stays put.

In-app agent: your agent, your tokens, your configuration and, yes, your bill.

Why it matters over the next few years

The expectation is that over roughly the next 24 to 36 months, visitors will show up with their own agent, already loaded with their context and memory, and take it everywhere. WebMCP meets that visitor at the front door without taking away the visual interface that ordinary people still want.

Where it makes sense to build first

Compatibility-driven commerce, where every specification has to match, like cameras or coffee gear.

Software admin surfaces, like consoles, analytics dashboards and marketing tools.

Regulated work such as insurance and banking self service, using read-only tools that surface the right information and send people to the right page.

Internal tools for your own team. Honestly, that's the easiest place to start today.

The business idea hiding inside it

The obvious service business here is making ordinary business websites agent ready: law firms, home services, clinics and the like. Build a first version of the tools that matter, such as request a quote or book a consultation. Then charge a setup fee plus a monthly retainer for monitoring and evaluation. The pitch is simple. Agents are a new class of visitor, and those visitors book jobs.

What to actually take away

If your website has anything transactional on it, the useful question isn't whether AI can read your page anymore. It's which five actions you'd let a visitor's agent perform directly, and whether your site can hand those over cleanly.

Source: The Startup Ideas Podcast, posted on X on 26 August 2026.