WebMCP is Cloudflare’s developer preview for exposing website tools that compatible browser AI agents can discover and call.

Who should use WebMCP?

It is best for developers building agent ready websites and experimenting with MCP based browser workflows.

What does WebMCP help with?

It helps websites expose explicit actions to browser agents instead of requiring agents to guess how to navigate pages.

How is WebMCP priced?

WebMCP is presented as a developer preview. No separate fixed WebMCP price was published, so underlying Cloudflare plan requirements should be checked.

What makes WebMCP different?

It exposes website tools through an edge injected bridge without requiring the described preview setup to change origin code.

What should buyers check before using WebMCP?

Check browser and agent support, security boundaries, exposed actions, and preview stability.

WebMCP

WebMCP lets compatible AI agents discover and call explicit website tools.

Visit Website

What is WebMCP?

TL;DR

Agent callable website tools
Edge injected WebMCP bridge
MCP server connection support

Explore with AI

About

WebMCP is Cloudflare’s developer preview for giving websites an interface that browser based AI agents can discover and call. Instead of forcing an agent to navigate a human focused page by guessing clicks and fields, WebMCP lets a site expose a set of tools that describe actions the agent can use. Cloudflare’s implementation adds a small bridge at the edge when WebMCP is enabled for a domain. The bridge can register tool packs in the browser, and the preview includes support for content credentials and an MCP server connection. Cloudflare says the setup does not require changes to the origin code, and the exposed tools can be discovered by Browser Run or other compatible browser agents. Sites choose which capabilities they want to expose. The main differentiation is the attempt to make existing websites callable by agents without rebuilding their application around a separate agent API. WebMCP is still an experimental developer preview, and the underlying web standard and available tool packs are evolving. Buyers should therefore evaluate browser support, agent client compatibility, security boundaries, and the exact actions exposed before enabling it on a production domain. For FutureStack, WebMCP belongs in Developer Tools because its primary buyer intent is making websites usable by AI agents. It is best for developers experimenting with agent ready interfaces, MCP integrations, and browser automation that can act through explicit site tools.

Use Cases

Agent Ready Websites

Expose explicit website actions that compatible AI agents can discover and call.

Tool Pack Registration

Register selected website capabilities so browser agents can work with defined tools instead of guessing interface actions.

MCP Browser Integration

Connect supported MCP and browser agent workflows to website capabilities through the WebMCP bridge.

Controlled Agent Actions

Choose which website capabilities are exposed to agents and keep the available action surface explicit.

Key Features

Agent callable website tools
Edge injected WebMCP bridge
MCP server connection support
Browser agent tool discovery

Featured Tools

Wispr Flow

Voice-First Dictation

We may earn commissions from links to support our work. Learn more.