WebMCP for docs
WebMCP lets a browser agent search your documentation, read indexed documents, and request Biel.ai answers while visiting a page with the Biel.ai widget.
The agent and browser must support WebMCP. Other MCP clients can connect through your hosted MCP server without visiting the page.
Requirements
- A Biel.ai project with indexed content and MCP access: a 14-day trial, Professional, or a higher plan. See plans.
- The latest Biel.ai widget. Update your widget if you use a pinned version or bundle it with your site.
- An HTTPS page and a browser agent that supports WebMCP.
WebMCP is experimental and browser support is limited. See Chrome's WebMCP guide for availability and testing instructions. Visitors using other browsers can use the widget as usual.
Enable WebMCP
- Open your project in Biel.ai and go to Settings > MCP.
- Select Enable MCP server and Enable WebMCP, then click Save.
- Load a page containing your widget in a supporting browser.
Enable WebMCP is on by default for new and existing projects. It takes effect when MCP is enabled and your plan includes MCP access. No additional embed code is needed, and the widget dialog can stay closed.
Turn off Enable WebMCP to disable browser tools while keeping hosted MCP available. Turning off Enable MCP server disables both. Downgrading to Starter also disables WebMCP.
Available tools
| Tool | What it does |
|---|---|
biel_search | Searches your indexed pages, files, repositories, and OpenAPI documents. Returns matching text and source references. |
biel_get_document | Reads the indexed text of a document found by search. |
biel_ai | Asks Biel.ai to generate an answer with sources. |
The agent normally searches, reads relevant documents if it needs more context, and writes its own answer with citations. Use biel_ai when you want a Biel.ai-generated answer. Each AI call starts a separate conversation from the visitor's widget chat.
Searches, document reads, and AI answers share your team's interaction allowance. Reading a long document may require several requests, each of which counts toward usage.
Try it
Open your documentation site in a supporting browser agent and ask:
Use this site's Biel tools to find how API authentication works. Read the relevant documentation and explain the steps with source links.
The agent should discover the tools, search your indexed content, and use the results in its answer. Tools become available when the agent visits the page. Installing the widget does not add your site to every MCP client's tool list.
Private projects
Private projects require Business or Enterprise. The widget's API key needs projects_read to load the project, search for search and document reads, and chats_create for AI answers.
A key included in a page is visible to visitors who can access it. Keep private-project widgets on a site restricted to the intended readers. See API keys and security.
Troubleshooting
| Problem | What to do |
|---|---|
| The agent cannot find the tools | Check browser and agent support, update the widget, and confirm both MCP settings and your plan access. Widgets using disable-input="true" or fetch-data="false" do not expose tools. |
| The widget is inside an iframe | The parent page must allow the tools permission for that iframe. Follow the browser's WebMCP setup instructions. |
| A call is denied | Check API key permissions, allowed domains, and your team's usage allowance. |
| A document is unavailable | Search again. If it is still unavailable, recrawl the source in Biel.ai. |
| An AI call asks for terms acceptance | Open the widget and accept its chatbot terms. |
Hiding the widget's Connect button does not disable WebMCP. Use Settings > MCP > Enable WebMCP to turn it off.