tela: team wiki with MCP for agents
tela
A self-hosted markdown wiki with a built-in MCP server: agents search, read and write pages under scoped permissions
- 95 ★ on the repository
- Last commit
- AGPL-3.0
Broad access
Why this level
- The token lets the agent read and, with granted rights, edit and move your team wiki pages
- Page content enters the model context and may contain internal data
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/telaDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The token lets the agent read and, with granted rights, edit and move your team wiki pages
- Page content enters the model context and may contain internal data
This is third-party code. Review the repository files before installing.
What it does
tela is a team wiki on Markdown that you can self-host. The backend is Go with PostgreSQL, the editor is React 19 with Milkdown, and real-time collaboration runs over Yjs, with comments, backlinks and revision history. A page body is always plain Markdown in `pages.body`, with sync over WebDAV and export to zip and PDF. The MCP server is built into the backend at `/api/mcp` and is not a separate process. It accepts a personal access token in a header and lets agents search, read and create pages, move them and add comments. Write permissions are set per tool and enforced on the server. HTTP-capable clients connect directly and sign in through OAuth, and for the rest there is the `tela-mcp` package, a thin stdio-to-HTTP proxy that needs Node 20 or later. PostgreSQL full-text search works out of the box, and with an embedder connected there is semantic search on `pgvector` and answers over your docs. The Atlas feature drafts and maintains pages from your sources. Deployment needs Docker and make: `make setup`, then `make up`.
Who it is for. Engineering and support teams that keep documentation in their own wiki and want Claude Code and Cursor to read and extend it.
Good fit when
- You want a wiki on your own server where Markdown stays the primary format
- An agent should search documentation and answer with page links
- You want an agent to add to pages without the right to delete
- Docs go stale and need to be pulled up to date from code
- You want to open a space as a login-free blog with per-author home pages
Not a fit when
- You want a wiki without your own infrastructure: deployment needs Docker, PostgreSQL and Caddy, and there is a cloud option at telawiki.com
- You want a proprietary license: the core is AGPL-3.0, and embedding in a closed service needs a commercial license
- You only need agent access to an existing tracker: separate servers exist for that
Example request
Find pages about releasing in our wiki, answer how to deploy with page links, and add a comment to the outdated one.MCP
- Transport
- http, stdio
- Authentication
- API key
Environment variables
TELA_BASE_URLrequired- Origin of the tela instance
TELA_API_KEYrequired, secret- Personal access token tela_pat_
Limitations
The core is AGPL-3.0: if you run a modified version as a network service, you must offer users the source. The `tela-mcp` package is `AGPL-3.0-only`; it implements no tools itself and only forwards the protocol to `/api/mcp`. Semantic search needs an embedder and the `pgvector` extension; without them only full-text search works. OAuth sign-in for Claude.ai and ChatGPT is enabled by configuring WorkOS AuthKit, otherwise access goes through a personal token. The `generate_deck_image` tool returns 503 until an image service URL is set. The stdio proxy requires Node 20 or later.
How to disable. Remove the `tela` entry from the client configuration and revoke the token under Settings, API Keys. The server itself is stopped with `make down`.
FAQ
How do I connect tela to Claude Code?
For HTTP clients use `https://telawiki.com/api/mcp` or your server's `/api/mcp`, with OAuth sign-in. For stdio use `npx -y tela-mcp` with `TELA_BASE_URL` and `TELA_API_KEY`.
Where is page content stored?
In `pages.body` as plain Markdown, with no block table. Data can sync over WebDAV and export to zip or PDF.
Can I give an agent read-only rights?
Yes. Write permissions are per tool and enforced on the server, and a personal token is issued under Settings, API Keys.
What is needed to self-host?
Docker with Compose and make. `make setup` and `make up` build the images and bring up the stack behind Caddy at `http://localhost:8780`, and the `/setup` wizard creates the administrator.
How do I enable semantic search?
Connect an embedder and enable `pgvector`. Compose has an optional profile with Ollama, and the embedder address is set with `TELA_RAG_EMBED_URL`.
Discussion
No questions or reviews yet.
Related
MCP serversA team wiki living in Git with a 51-tool MCP server: agents read and edit pages, tables and boards.
An MCP server for Yandex Wiki: read pages by slug or URL, create, update and append, with a read-only mode
The official Kibela MCP server searches, reads and edits notes, folders and comments of your wiki straight from an assistant chat
A Go MCP server for reading Yandex Tracker and Yandex Wiki: issues, queues, sprints, comments, pages and dynamic tables
An MCP server for a BookStack wiki: read and search by default, writes enabled separately, rights taken from the token.
MCP server for the knowledge base Beever Atlas builds from Slack, Discord, Teams and Mattermost chats: cited answers, channel wikis, a graph
README in short
The README explains how tela differs, then gives a Docker Compose quick start, one-click cloud deploy, useful `make` targets and optional semantic search. Environment variables, authentication (MCP OAuth and federated sign-in), connecting agents over MCP and the AGPL-3.0 licence terms with a commercial option follow.