Your documentation explains how to install your SDK, authenticate API requests, and configure your product. WebMCP gives browser agents a way to find and use those instructions while helping a reader on your site.
Biel.ai adds WebMCP to your documentation through its existing widget. You connect your sources, and Biel makes that documentation available to supporting browser agents.
What is WebMCP?
WebMCP is a proposed web standard that lets websites expose structured tools to AI agents. A website can offer a search action, for example, with defined inputs and results that an agent can use to complete a task. See Chrome’s WebMCP overview.
For documentation sites, this gives agents a way to request relevant product information from the site itself. They can search for a guide, read its content, and use it to answer a question with source links.
The agent discovers these tools when it visits the page in a supporting browser. Browser and agent support are both required.
Example: help a developer configure an SDK
A developer opens your documentation with a browser agent and asks:
Check the JavaScript SDK docs and explain how to install it and authenticate. Include the supported runtime and links to the instructions.
With Biel’s WebMCP integration enabled, the agent can:
- Search your indexed documentation for installation and authentication guidance.
- Read the relevant guides to check the prerequisites and configuration steps.
- Explain the setup using those sources and link back to your docs.
The developer gets an answer based on your product documentation within their browser workflow. Your team continues maintaining the same guides that human readers use.
Try this with a task your docs already cover. Compare the answer with the source page to check that the agent includes the right prerequisites and instructions.
Add WebMCP to your docs with Biel.ai
Biel.ai provides a managed WebMCP integration for documentation sites. It indexes your connected content and makes it available through the widget, so you can add browser-agent access to your existing documentation platform.
If you already use Biel, open your project in the dashboard and go to Settings > MCP. Select Enable MCP server, leave Enable WebMCP on, and save. Load your docs with the latest widget to make the tools available in supporting browsers.
For a new project, connect your documentation and install the Biel widget first. There is no extra WebMCP embed code to add.
WebMCP is on by default for new and existing projects. You can turn it off from Settings > MCP while keeping hosted MCP enabled.
Requirements
- Indexed documentation in your Biel.ai project and the latest widget installed on your site.
- MCP access through the 14-day trial, Professional ($150/month), or a higher plan. Downgrading to Starter disables WebMCP. See pricing.
- An HTTPS page and a browser-agent combination that supports WebMCP. The standard is experimental. Check Chrome’s current browser requirements before testing.
- Authorized access for private documentation. Private projects require Business or Enterprise. Keep private widgets on a site restricted to the intended readers.
Tool calls use your team’s interaction allowance. The WebMCP setup guide covers access settings and troubleshooting.
Frequently asked questions
Can I keep my current documentation site?
Yes. Biel works with existing documentation sites, including Docusaurus, MkDocs, and Sphinx. Add the widget to give supporting browser agents access to your indexed docs.
How does WebMCP differ from hosted MCP?
WebMCP serves agents visiting your site. Our hosted MCP server for docs connects AI clients to the same project from an editor or terminal. See connecting docs to Claude Code for an example, or MCP and llms.txt for documentation for other ways to share docs with agents.
Enable WebMCP for your documentation and try it with one of your getting-started guides.