Biel.ai

ai.biel由 biel.ai 发布官方发布者v2.0.0更新于 Oct 27, 2026

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

已验证Streamable HTTP可网页运行知识与记忆开发者工具

概览

AI 生成的概览

Biel.ai MCP 服务器,让助手检索你已索引的技术文档、读取完整文档,并获得带来源引用的回答。

可以做什么
  • 对已索引文档进行关键词与语义混合检索,覆盖网页、上传文件、代码仓库和 OpenAPI 来源
  • 按检索结果中的文档 ID 读取完整索引文本,无需访问原始站点
  • 请求 Biel.ai 生成带来源链接的对话式回答
  • 返回片段文本、来源类型、文档 ID 以及页码或表格位置等引用信息
适用场景
适合希望 Claude Code、Codex、Cursor 或 ChatGPT 等 AI 客户端基于你自己的产品或 API 文档、并附上引用来源来回答问题的场景。
运行要求
需要 mcp.biel.ai 的远程 Streamable HTTP 端点,并在包含该功能的 Biel.ai 套餐中启用托管 MCP,同时需要 Biel.ai 账号和已索引的来源。公开项目无需密钥;私有项目需在 URL 中提供具有 search 与 chats_create 权限的 api_key 查询参数,配置了允许域名时还需 domain 参数。不支持原生 HTTP 的客户端需借助 mcp-remote 等桥接。也可选用 Python 包或 Docker 自托管。
安装前请注意
私有项目会在端点 URL 中携带 api_key,应将该 URL 视为凭据,避免放入共享配置。生成的回答和检索内容仍可能有模型错误,需核对检索文本与引用。MCP 提供的是已索引内容,文档变更后需在 Biel.ai 中刷新来源。自托管需自行运行服务器。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Biel.ai,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

[Biel.ai]

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.

[Demo]

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:

text
Use biel_search to find our API authentication instructions. Read relevantresults 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.

Choose generated answers or search

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:

json
{"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:

json
{"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

bash
# Clone and run locallygit clone https://github.com/TechDocsStudio/biel-mcpcd biel-mcppip 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:

bash
pip install "biel-mcp @ git+https://github.com/TechDocsStudio/biel-mcp.git@VERSION"
python
from biel_mcp.server import app

Docker deployment

bash
# Docker Compose (recommended)docker-compose up -d --build
# Or Docker directlydocker build -t biel-mcp .docker run -d -p 7832:7832 biel-mcp

Support

来源:README.md,提交 2337554

工具

0
SourceWeft 尚未读取此服务器的工具。

版本历史

1
  1. v2.0.0最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式必需10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分