Tela

io.github.zcagPublished by GitHub account zcagv0.7.5Updated Nov 2, 2026

Self-hostable team wiki; agents read & write it via MCP; Atlas turns your repo into a cited wiki.

VerifiedStreamable HTTPWeb executableProductivity & Workflow Knowledge & Memory

Server details

Identifier: io.github.zcag/tela
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account zcag for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.zcag%2Ftela.svg)](https://sourceweft.com/mcp/io.github.zcag%2Ftela?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Proxy or remote endpoint for Tela, a self-hostable team wiki, letting an assistant list spaces, read and search pages, and create or move pages.

What you can do: List and browse wiki spaces and pages
Read a page and search it by keyword or semantic search
Create pages, move pages and add comments
Expose pages and spaces as tela:// resources for context
Forward the full MCP surface (tools, resources, prompts) from the Tela backend
When to use it: Use it when your team keeps documentation in a Tela wiki and you want an assistant to look up, cite or write pages there. Most hosts can connect straight to the HTTP endpoint; the npm proxy is only for stdio-only hosts.
Requirements: A Tela instance (hosted at telawiki.com or self-hosted) and a personal access token created in Settings, API Keys. Remote use needs the endpoint URL plus an Authorization bearer header; the npm proxy needs Node.js and both TELA_BASE_URL and TELA_API_KEY set at spawn time.

Before you install

The token grants access to your wiki with read, write or admin scope, so treat it as a secret and prefer the narrowest scope. The assistant can create and move pages and add comments, which changes shared team content. Scope and per-space restrictions are enforced by the backend, not the client.

Installation

In SourceWeft

Open Tela in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.zcag%2Ftela/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "tela": {
      "type": "http",
      "url": "https://telawiki.com/api/mcp"
    }
  }
}

README

tela-mcp

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.

Most hosts don't need this package

Modern MCP hosts speak Streamable HTTP transport directly — point them at the endpoint and skip the proxy entirely:

# Claude Codeclaude mcp add --transport http tela https://telawiki.com/api/mcp \  --header "Authorization: Bearer tela_pat_..."

# Claude Codeclaude 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.

Using the proxy (stdio-only hosts)

Add to your .mcp.json:

json

{  "mcpServers": {    "tela": {      "command": "npx",      "args": ["-y", "tela-mcp@latest"],      "env": {        "TELA_BASE_URL": "https://telawiki.com",        "TELA_API_KEY": "tela_pat_..."      }    }  }}

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

Tool & resource catalog

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.

Auth

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).

Develop

cd mcpnpm installnpm run build            # tsc → dist/server.jsnpm run test:integration # live proxy↔backend E2E (needs a running backend; use `make test-mcp-integration` from the repo root)

cd mcpnpm installnpm run build            # tsc → dist/server.jsnpm 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).

License

AGPL-3.0-only.

Source: mcp/README.md at commit 634b7e8

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v0.7.5LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts