Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Self-hostable team wiki; agents read & write it via MCP; Atlas turns your repo into a cited wiki.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
TELA_BASE_URL, TELA_API_KEY标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://telawiki.com/api/mcp打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"tela": {
"command": "npx",
"args": [
"-y",
"tela-mcp"
],
"env": {
"TELA_BASE_URL": "your-value",
"TELA_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http tela https://telawiki.com/api/mcpclaude mcp add tela --env TELA_BASE_URL=your-value --env TELA_API_KEY=your-value -- npx -y tela-mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"tela": {
"url": "https://telawiki.com/api/mcp"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"tela": {
"command": "npx",
"args": [
"-y",
"tela-mcp"
],
"env": {
"TELA_BASE_URL": "your-value",
"TELA_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"tela": {
"type": "http",
"url": "https://telawiki.com/api/mcp"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"tela": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"tela-mcp"
],
"env": {
"TELA_BASE_URL": "your-value",
"TELA_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://telawiki.com/api/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 zcag 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:TELA_BASE_URL, TELA_API_KEY
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(0.7.5)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Signoff
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A thin stdio↔HTTP proxy to a Tela instance's built-in MCP server.
As of v0.7, the MCP server lives inside the Tela backend at {TELA_BASE_URL}/api/mcp (Streamable HTTP, spec-compliant). This npm package no longer implements any tools itself — it's a dumb pipe that forwards the entire MCP protocol (tools, resources, prompts, notifications) over stdio to that endpoint, injecting your personal access token as a bearer header. Because it holds no tool knowledge, the backend's MCP surface can grow without this package ever changing — there is no second implementation to drift.
Modern MCP hosts speak Streamable HTTP transport directly — point them at the endpoint and skip the proxy entirely:
# Claude Code
claude mcp add --transport http tela https://telawiki.com/api/mcp \ --header "Authorization: Bearer tela_pat_..."
Cursor, VS Code, Zed, and the Anthropic Messages API mcp_servers connector likewise accept a URL + bearer header. Use this npm package only for stdio-only hosts that can't speak HTTP transport.
Add to your .mcp.json:
{
"mcpServers": { "tela": { "command": "npx", "args": ["-y", "tela-mcp@latest"], "env": { "TELA_BASE_URL": "https://telawiki.com", "TELA_API_KEY": "tela_pat_..." } } } }
| Var | Purpose |
|---|---|
TELA_BASE_URL | Origin of the Tela instance (e.g. https://telawiki.com or http://localhost:8780). The proxy connects to {TELA_BASE_URL}/api/mcp. |
TELA_API_KEY | Personal access token (tela_pat_…), forwarded as Authorization: Bearer. Create one in Settings → API Keys. |
Both must be set at spawn time, or the process exits non-zero before the MCP handshake.
The tools (list_spaces, get_page, search, semantic_search, create_page, move_page, add_comment, …), the tela://page/{id} / tela://space/{id} resources, and the read/write/admin scope model are all defined and documented in the backend, not here. Scope and per-space restrictions are enforced server-side; failures arrive as the usual {error, code, status} envelope in the tool result. See the project Showcase: https://telawiki.com/spaces/1/pages/19.
This package authenticates with a static personal access token (PAT), which works with the Messages API connector and any host that accepts a bearer header. The OAuth "Connect" flow used by the Claude.ai / ChatGPT consumer apps is a separate, server-side capability (it does not involve this package).
cd mcp
npm install npm run build # tsc → dist/server.js npm run test:integration # live proxy↔backend E2E (needs a running backend; use make test-mcp-integration from the repo root)
The proxy is ~40 lines over the official @modelcontextprotocol/sdk transports. Exhaustive per-tool coverage lives in the Go backend's e2e MCP tests (backend/internal/api/mcp_test.go).
AGPL-3.0-only.