Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Query your product docs from AI tools. Source-cited answers from your indexed documentation.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.biel.ai/v2/{project_slug}/mcp地址中有只有你知道的 {…} 部分(例如你的账户),请复制后自行填写。
在终端中运行这条命令
claude mcp add --transport http biel-ai 'https://mcp.biel.ai/v2/{project_slug}/mcp'地址中有只有你知道的 {…} 部分(例如你的账户),请复制后自行填写。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"biel-ai": {
"url": "https://mcp.biel.ai/v2/{project_slug}/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
地址中有只有你知道的 {…} 部分(例如你的账户),请复制后自行填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"biel-ai": {
"type": "http",
"url": "https://mcp.biel.ai/v2/{project_slug}/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.biel.ai/v2/{project_slug}/mcp地址中有只有你知道的 {…} 部分(例如你的账户),请复制后自行填写。
菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 biel.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
这个地址需要填入你自己的账户信息,所以我们无法替你检查
这个地址需要填入你自己的账户信息,所以我们无法替你检查
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(2.0.0)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, FlyDocs
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
Open your project in Biel.ai, go to Settings > MCP, enable the MCP server, and save. Copy the complete endpoint supplied for your project.
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.
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}
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.
For advanced users who prefer to run their own MCP server instance:
# Clone and run locally
git clone https://github.com/TechDocsStudio/biel-mcp cd biel-mcp pip install . biel-mcp
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 Compose (recommended)
docker-compose up -d --build
docker build -t biel-mcp . docker run -d -p 7832:7832 biel-mcp