Docs MCP server

Connect ChatGPT, Claude, and coding assistants to your documentation through Biel.ai's hosted Model Context Protocol (MCP) server. Your assistant can search indexed content, read relevant documents, and answer with sources.

For browser agents visiting your documentation site, see WebMCP.

Requirements

• A Biel.ai project with indexed content.
• MCP access during your 14-day trial, or on Professional or a higher plan. See plans.
• An AI client that supports remote MCP connections.
• For private projects, Business or Enterprise and a project API key.

Setup

1. Open your project in Biel.ai and go to Settings > MCP.
2. Select Enable MCP server and click Save.
3. Copy the MCP endpoint shown on the page and add it to your AI client.

For client-specific instructions, see the ChatGPT plugin guide or Claude connector guide.

Connect from the widget

You can also open the widget's Connect menu:

• MCP URL copies the endpoint to paste into another client's MCP settings.
• Codex copies a setup command. Run it in your terminal.
• Claude Code copies a setup command. Run it in your terminal.
• Copilot (VS code) opens VS Code's MCP setup flow.
• Cursor opens Cursor's MCP setup flow.

Manual configuration

Add a remote MCP server in your client's settings and paste the complete endpoint supplied by Biel.ai. Choose Streamable HTTP if the client asks for a transport.

For example, a project endpoint may look like this:

https://app.biel.ai/mcp/YOUR_PROJECT_SLUG

Use the URL supplied for your project and follow your client's remote MCP setup instructions.

Available tools

Tool	What it does
biel_search	Searches 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. Supports follow-up questions within the connection's conversation.

The assistant normally searches, reads relevant documents if it needs more context, and writes its own answer with citations. Document reads return the text indexed by Biel.ai.

Try asking:

Search our docs for API authentication. Read the relevant documentation and explain how to rotate an API key, with source links.

When you want Biel.ai to generate the answer, ask:

Ask Biel.ai how to configure single sign-on.

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.

Connection access

Public projects do not require an API key. For a private project, create an API key restricted to that project and add it to the connection URL as api_key.

URL parameter	When to use it
api_key	Required for private projects. The key needs search for search and document reads, and chats_create for AI answers.
domain	Required when your project restricts allowed domains. Use an allowed origin, such as https://docs.example.com.
metadata	Optional label identifying the client, such as claude.

For example, a public project with domain restrictions can use:

https://app.biel.ai/mcp/YOUR_PROJECT_SLUG?domain=https%3A%2F%2Fdocs.example.com

URL-encode parameter values. Keep URLs containing API keys private: anyone with the URL can use the key's project access. Do not include them in public listings or shared setup files.

Widget customization

Hide connect button

Add hide-connect-button="true" to your widget to hide its Connect menu.

To disable access, open your project in the Biel.ai dashboard and go to Settings > MCP. Turn off Enable MCP server to disable both hosted MCP and WebMCP. Turn off only Enable WebMCP to disable browser tools while keeping hosted MCP available.

Custom MCP server URL

Add mcp-server-url="https://mcp.example.com/your-endpoint" to your widget to show a different endpoint in the Connect menu. This setting applies only to hosted MCP.

See widget customization for more settings.

Self-hosted option

To run your own MCP server, follow the self-hosting guide.

Troubleshooting

Problem	What to do
The client cannot connect	Copy the endpoint again from Settings > MCP. Check that MCP is enabled, your plan includes it, and the client can reach the endpoint.
The assistant does not search your docs	Enable the connection in your client and explicitly ask it to use biel_search. Check that your project has indexed content.
Access is denied	Check the API key's project access and permissions, allowed domains, and your team's usage allowance.
A document is unavailable	Search again for a current result. If it is still unavailable, recrawl the source in Biel.ai.
Tools are missing or the session has expired	Refresh or reconnect the MCP server in your client, then start a new conversation.