Log inSubmit server
Tela logo

Tela

by zcag

Search, read, and write markdown wiki pages through tela's built-in MCP server.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Tela

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "zcag-tela": {
      "command": "npx",
      "args": [
        "-y",
        "tela-mcp"
      ],
      "env": {
        "TELA_PUBLIC_BASE_URL": "YOUR_VALUE_HERE",
        "TELA_SHARE_SECRET": "YOUR_VALUE_HERE",
        "TELA_API_KEY_SECRET": "YOUR_VALUE_HERE",
        "TELA_PG_PASSWORD": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Overview

zcag/tela MCP server connects AI agents to a self-hosted tela team wiki backed by Go and PostgreSQL. Agents can search pages, read content, create or update wiki pages, and follow backlinks through the `/api/mcp` endpoint. Ranked PostgreSQL full-text search is available by default, while pgvector-backed semantic retrieval can be enabled with an embedder. Use it when agents need controlled access to a team's canonical markdown documentation.

Use cases

  • Search team documentation for answers
  • Read related wiki pages through backlinks
  • Draft new pages from agent conversations
  • Update operational documentation
  • Retrieve semantically related Markdown content

Key features

  • Markdown-native wiki access
  • Ranked PostgreSQL full-text search
  • Optional pgvector semantic retrieval
  • Page read and write operations
  • Backlink traversal
  • Scoped per-tool write permissions

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

24/24 checks healthy over the last 84d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars89Stargazers on the source repository.
npm downloads168Package downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Tela works

What zcag/tela MCP server does

The zcag/tela MCP server gives agents access to a tela wiki as both a knowledge source and an authoring surface. It works with tela's markdown-native page store, where page bodies remain canonical Markdown rather than being converted into a proprietary block format. Agents can find relevant pages, retrieve their contents, create documentation, and update existing pages.

The wiki is backed by a Go application and PostgreSQL. Search combines ranked PostgreSQL full-text retrieval with optional semantic search through pgvector. Page relationships can also be explored through backlinks, which helps an agent move from a matching page to related documentation.

How it works

The MCP interface is built into tela's backend at /api/mcp, rather than being a separate add-on to the wiki. An agent connects to the tela instance and operates against the same content that users edit in the browser. Write access can be scoped per tool, allowing deployments to distinguish between agents that may only read documentation and those permitted to author or revise pages.

Full-text search works without an embedding service. Semantic retrieval requires an embedder and pgvector; the bundled deployment can run Ollama as an optional embedding service. Atlas is tela's documentation engine for generating and maintaining wiki pages from sources such as Git repositories and Jira, complementing the direct MCP workflow.

Setup and configuration

A self-hosted tela deployment uses Docker Compose and Make. Clone the repository, run make setup to create the environment file and secrets, set the public URL, then start the stack with make up. The service is exposed through Caddy on port 8780 by default, and the first launch provides a setup wizard unless bootstrap admin credentials are configured.

The deployment requires a public base URL, share-link signing secret, API-key signing secret, and PostgreSQL password. Keep the signing secrets stable: changing them invalidates existing share cookies or personal access tokens. The tela-mcp npm package can also be launched with npx tela-mcp.

Tools and capabilities

  • Search wiki content using ranked PostgreSQL full-text search.
  • Use optional semantic retrieval backed by pgvector and an embedding service.
  • Read Markdown page content from the connected tela wiki.
  • Create and update wiki pages through agent-authorized write tools.
  • Traverse backlinks to discover related pages.
  • Work against the same pages maintained by browser users and Atlas.

Limitations and notes

Semantic search is optional; full-text search is the default retrieval path. Enabling semantic retrieval requires pgvector and an embedder, such as the optional Ollama service in the Compose setup. Write operations depend on the permissions granted to the connecting agent, so a read-only configuration will not support page authoring.

Self-hosting requires Docker with Compose and Make for the bundled deployment. Removing Docker volumes with make clean FORCE=1 deletes stored data, and rotating the API-key secret invalidates existing personal access tokens.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Tela

zcag/tela is an MCP server that connects AI agents to a self-hosted tela Markdown wiki backed by Go and PostgreSQL. Its main tools let agents search wiki content, read pages, write or update documentation, and traverse backlinks. Full-text search is built in, with optional semantic retrieval through pgvector.

Install the MCP package by running `npx tela-mcp`; for a complete self-hosted tela instance, clone the repository, run `make setup`, configure `deploy/.env`, and start it with `make up`. The bundled deployment uses Docker Compose and exposes the service on port 8780 by default.

Yes, zcag/tela works with Cursor. The built-in MCP server is intended for Claude, Cursor, and other agents, and exposes the tela wiki through the backend MCP endpoint.

Yes, semantic search is available when pgvector and an embedding service are configured. PostgreSQL full-text search works without that additional setup; the bundled Compose deployment can run Ollama as an optional embedder.

Yes, agents can author and update wiki pages when the corresponding write permissions are granted. tela supports scoped, per-tool write access, so deployments can restrict an agent to reading or allow controlled documentation changes.

Related MCP servers

All in Knowledge & Memory All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTela AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/zcag-tela?style=directory)](https://allmcps.com/mcp/zcag-tela)
HTML Embed
<a href="https://allmcps.com/mcp/zcag-tela"><img src="https://allmcps.com/api/badge/zcag-tela?style=directory" alt="Tela on AllMCPs" /></a>