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 分