English Français العربية

Biel.ai

Official registry Productivity

Query your product docs from AI tools. Source-cited answers from your indexed documentation.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http biel-ai 'https://mcp.biel.ai/v2/{project_slug}/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "biel-ai": {
            "type": "http",
            "url": "https://mcp.biel.ai/v2/{project_slug}/mcp"
        }
    }
}
Remote (sse)
Claude Code 
claude mcp add --transport sse biel-ai 'https://mcp.biel.ai/sse?project_slug={project_slug}&domain={domain}'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "biel-ai": {
            "type": "sse",
            "url": "https://mcp.biel.ai/sse?project_slug={project_slug}&domain={domain}"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Biel.ai MCP Server
  2. Getting started
  3. Choose generated answers or search
  4. Troubleshooting
  5. Self-hosting (Optional)
  6. Support

Biel.ai MCP Server

Give AI assistants context from technical documentation

Biel.ai turns technical documentation into answers for users and context for AI agents, with links back to the sources. This MCP server connects Claude Code, Codex, Cursor, and other compatible clients to documentation indexed in a Biel.ai project.

The usual workflow is to search for relevant content, retrieve indexed documents when more context is needed, and answer in the calling AI assistant. Biel.ai can also generate an answer when you explicitly request one. Source grounding does not eliminate model error; check the retrieved content and references.

Requires a Biel.ai account, indexed sources, and hosted MCP enabled on a plan that includes it. Create an account and follow the MCP setup guide.

Getting started

1. Enable MCP and copy your endpoint

Open your project in Biel.ai, go to Settings > MCP, enable the MCP server, and save. Copy the complete endpoint supplied for your project.

2. Connect your AI client

Use the canonical documentation for client-specific steps:

The example configuration uses mcp-remote as a bridge for clients without native Streamable HTTP support. Clients with native HTTP support should connect directly using their own configuration format.

3. Verify retrieval

Confirm the client discovers biel_search, biel_get_document, and biel_ai. Ask a question your indexed documentation covers:

Use biel_search to find our API authentication instructions. Read relevant
results with biel_get_document and explain the required headers with source links.

Check the retrieved text and citations against the documentation. MCP serves indexed content; refresh sources in Biel.ai after documentation changes and search again for current document IDs.

The server exposes three tools:

  • biel_ai: ask Biel.ai to generate an answer, with conversational context. Existing calls using message continue to generate answers.
  • biel_search: hybrid keyword and semantic search over indexed web pages, uploaded files, repositories and OpenAPI sources, without answer generation.
  • biel_get_document: read the complete indexed text of a document returned by search.

Call biel_search with a natural-language question or search terms:

{"query": "How do I authenticate with the SDK?", "limit": 5}

Search requests the API's search_type=hybrid&source_types=all. The REST API defaults to search_type=keyword, independently of the selected sources. Results include chunk text, source type, a document_id, and any page/sheet reference; non-URL documents are cited by title and location. The limit argument controls how many chunks are returned (default 5, maximum 20).

Use biel_get_document with a search result's document_id to read the complete indexed document without visiting its source site:

{"document_id": "DOCUMENT_ID_FROM_SEARCH", "limit": 20}

Troubleshooting

Public projects do not need an API key. Private projects require an api_key query parameter with search permission for retrieval and chats_create for generated answers.

A domain query parameter is needed when allowed domains are configured. See connection parameters before connecting a private or domain-restricted project. Treat a URL containing a key as a credential and keep it out of shared configuration.

Self-hosting (Optional)

For advanced users who prefer to run their own MCP server instance:

Local development
# Clone and run locally
git clone https://github.com/TechDocsStudio/biel-mcp
cd biel-mcp
pip install .
biel-mcp
Use as a Python package

Applications that host their own ASGI stack can install the server directly from a tagged revision and import its FastAPI application:

pip install "biel-mcp @ git+https://github.com/TechDocsStudio/biel-mcp.git@VERSION"
from biel_mcp.server import app
Docker deployment
# Docker Compose (recommended)
docker-compose up -d --build

# Or Docker directly
docker build -t biel-mcp .
docker run -d -p 7832:7832 biel-mcp

Support

Frequently asked questions

What is Biel.ai?

Query your product docs from AI tools. Source-cited answers from your indexed documentation.

How do I install Biel.ai?

It runs as a remote server. In Claude Code: claude mcp add --transport http biel-ai 'https://mcp.biel.ai/v2/{project_slug}/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Biel.ai need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Biel.ai open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Biel.ai?

It is published by TechDocsStudio. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.