Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Self-hostable team wiki; agents read & write it via MCP; Atlas turns your repo into a cited wiki.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
TELA_BASE_URL, TELA_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://telawiki.com/api/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"tela": {
"command": "npx",
"args": [
"-y",
"tela-mcp"
],
"env": {
"TELA_BASE_URL": "your-value",
"TELA_API_KEY": "your-value"
}
}
}
}Run this in your terminal
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-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"tela": {
"url": "https://telawiki.com/api/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"tela": {
"command": "npx",
"args": [
"-y",
"tela-mcp"
],
"env": {
"TELA_BASE_URL": "your-value",
"TELA_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"tela": {
"type": "http",
"url": "https://telawiki.com/api/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"tela": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"tela-mcp"
],
"env": {
"TELA_BASE_URL": "your-value",
"TELA_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://telawiki.com/api/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account zcag, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: TELA_BASE_URL, TELA_API_KEY
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (0.7.5) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, MemberVault MCP by usefulapi
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
List courses; add users to courses, remove course access or delete users in MemberVault.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.