wikidocumentationknowledge-basesearchmarkdown
Searches, reads, and writes markdown wiki pages through MCP, with PostgreSQL full-text and optional semantic retrieval.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Not yet automatically verified
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
Manual Client & Custom JSON ConfigExpand JSON â–¾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Overview
Use cases
Search team documentation from an agent
Read wiki pages during coding or support tasks
Write agent-generated pages into a canonical Markdown wiki
Generate maintained documentation from Git repositories and Jira
Key features
MCP access to search, read, and write wiki pages
Ranked PostgreSQL full-text search
Optional pgvector semantic retrieval
Backlink traversal
Scoped per-tool write permissions
Canonical Markdown page storage
Capabilities & Tool Schemas
Inspect callable tools, capabilities, and parameters exposed to AI agents by Tela.
Extracted Tool Capabilities
MCP access to search, read, and write wiki pages
Ranked PostgreSQL full-text search
Optional pgvector semantic retrieval
Backlink traversal
Scoped per-tool write permissions
Canonical Markdown page storage
How Tela works
What zcag/tela MCP server does
The zcag/tela MCP server exposes a Tela wiki to compatible agents. Agents can search the knowledge base, read pages, and author or update pages through the same system used by people in Tela’s web interface. Wiki content remains canonical Markdown in the pages.body field, so agent-written material is stored in the repository’s primary document format rather than a proprietary block structure.
Tela is a self-hostable team wiki backed by Go and PostgreSQL. In addition to agent access, the broader application provides nested page organization, comments, backlinks, revision history, live collaboration, and browser-based editing. These features matter when an agent’s output needs to become part of an actively maintained team knowledge base.
How it works
The MCP interface is part of the Tela backend and is available at /api/mcp; it is not described as a separate add-on service. Claude, Cursor, and other agents can use the endpoint to interact with the wiki. Tool permissions can be scoped so that write access is controlled per tool.
Search uses ranked PostgreSQL full-text search without requiring an embedding service. Tela can also use pgvector for semantic retrieval and documentation question-answering when an embedder is configured. The supplied deployment example uses Ollama with the qwen3-embedding:0.6b model, but semantic search is optional and full-text search remains available without it.
Tela also includes Atlas, a documentation engine that can turn existing source artifacts into maintained wiki pages. The provided description identifies Git repositories and Jira as Atlas inputs and says that generated pages include citations and coverage checks.
Setup and configuration
The zcag/tela MCP server can be run through the published tela-mcp npm package with npx. For a complete self-hosted Tela deployment, the repository provides a Docker Compose stack and a Make-based quickstart. The documented flow clones the repository, runs make setup, configures deploy/.env, and starts the services with make up.
The self-hosted stack requires Docker with Compose and Make. Required configuration includes the public instance URL, a secret for signed share-link cookies, a secret for personal access tokens, and the bundled PostgreSQL password. The application runs migrations on first boot and provides a setup wizard unless bootstrap administrator credentials are configured in advance.
The stack is exposed through Caddy on port 8780 by default. Tela can instead use an external PostgreSQL database by setting its full database URL. The repository also documents managed deployment options and a hosted free tier, but the MCP server’s deployment and authentication details should be checked against the target Tela installation.
Tools and capabilities
The zcag/tela MCP server supports these documented agent tasks:
- Search wiki content with ranked full-text retrieval.
- Use optional semantic retrieval through
pgvectorand an embedder. - Read existing wiki pages.
- Write or author wiki pages with scoped write permissions.
- Traverse backlinks when navigating related documentation.
- Work with Markdown that remains canonical in the database.
Use it for repository or team documentation workflows where agents need both retrieval and controlled authoring. It is less suitable if the required source is only an external system not connected to Tela, or if a deployment cannot provide the PostgreSQL-backed Tela application.
Limitations and notes
Semantic search is not enabled by default in the documented setup; it requires the optional embedder profile and additional configuration. Full-text search works without that component. The self-hosted deployment also depends on stable signing secrets: changing the share secret invalidates existing share cookies, while changing the API key secret invalidates personal access tokens.
The zcag/tela MCP server is part of a larger wiki application, so running only the npm launcher may not provide a knowledge base by itself. An accessible Tela instance and its MCP endpoint are still required for meaningful agent operations. The repository is licensed under AGPL-3.0.
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
GitHub stars
61
Stargazers on the source repository.
npm downloads
224
Package downloads in the last 30 days.
Last commit
3d ago
Most recent push to the default branch.
Directory activity
3 views
Config copies, upvotes, and views on AllMCPs.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Tela
AllMCPs Directory Badge
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 Preview
Markdown (GitHub README)
[](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>Technical Specs & Signals
CategoryKnowledge & Memory
PricingFree
10/10 checks healthy over the last 33d
60Quality signal: Good · 60/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools25/30
Adoption & activity10/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Supply-chain signal
No high-severity advisories surfaced by our automated scan.
Critical 0High 0Medium 0Low 0
Scanned 14d ago via OSV.dev · tela-mcp (npm)
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.