Your documentation,
in their AI tools.
Let Codex, Claude Code, and other compatible tools search and read your documentation through hosted MCP.
14 days free. No credit card required.
The documentation provides a Docusaurus plugin. Install it, then add your project ID to the plugin configuration.
The setup guide covers the remaining configuration and deployment steps.
Search and read your docs.
- Search the index
- Find relevant passages across the sources connected to a Biel project.
- Read the document
- Retrieve complete indexed text when a passage needs more context.
- Hosted endpoint
- Biel operates the MCP server. Your team maintains the documentation sources.
- Shared sources
- The website assistant and MCP endpoint retrieve from the same project index.
Connect your docs to an AI tool.
Index your documentation
Add your website, repository, or other supported sources.
Supported sourcesCopy the project endpoint
Get the hosted MCP URL from your Biel project.
MCP setupAdd it to your client
Connect the endpoint in a compatible AI tool.
Client connection guides
One endpoint.
Your choice of client.
Use a client that supports remote MCP. Client permissions and authentication requirements apply.
“It consistently delivers accurate results, and we've had no issues depending on it as part of our documentation experience.”
Questions
Which plan includes MCP?
MCP and WebMCP are included on every plan and share its interaction allowance. Private projects require Professional or higher and an API key. Compare plans.
Does Biel generate every answer in the AI client?
No. Biel supplies indexed documentation. The client decides when to call tools and how to use the retrieved content.
Can we mix public and private documentation?
Use separate projects when sources have different readers. Public endpoints need no key and should contain only public content.
Is this the same as WebMCP?
No. Hosted MCP provides a project endpoint for AI clients. WebMCP exposes tools on a page a browser agent is visiting. Read about WebMCP.