Compare
The MkDocs alternative that needs no build step
Last updated September 9, 2026
MkDocs — in practice Material for MkDocs — is the standard way to turn a docs/ folder into a documentation site, and it is very good at it. It is also markdown in a repo, with a build and a deploy behind every change, client-side keyword search, and no official MCP server. In November 2025 Material announced it was entering maintenance mode, with new development moving to a successor project. tela is a wiki instead: save and it is live, anyone can edit, and agents read and write it.
tela vs MkDocs, at a glance
| Feature | tela | MkDocs |
|---|---|---|
| Publishing | Save — the page is live | mkdocs build + deploy (gh-deploy, Read the Docs, CI) |
| Who can edit | Anyone — a WYSIWYG markdown editor in the browser | Markdown files in a git repo; no official editing UI |
| Search & AI answers | Built in — ranked full-text always, plus semantic Ask that cites its sources (self-host brings its own model) | Client-side keyword search (lunr); no AI answers documented |
| Agents read & write (MCP) | Built in — agents read and write, scoped per token, over a hosted endpoint | No official server (community plugins only) |
| Generate docs from your code | Yes — Atlas builds a cited, coverage-checked wiki from git repos and Jira | No — renders markdown you wrote (mkdocstrings pulls API reference from docstrings) |
| Keeping the files on disk | Two-way — mount /dav/ as a folder of .md files with any WebDAV client, or bisync it with rclone | They already are — a docs/ folder in your repo |
| Roadmap | Actively developed | Material for MkDocs is in maintenance mode since Nov 2025 — fixes only, features moved to its successor |
Why teams switch to tela
- No build, no deploy, no CI job — a page is live the moment you save it.
- Ask your docs a question and get an answer with citations, instead of client-side keyword search — and it searches attached PDFs too, not only the pages.
- You keep the folder either way: mount a tela space over WebDAV and your docs are still .md files you can edit in the editor you already use.
- Agents are first-class through a built-in MCP server, and Atlas drafts pages straight from your repos.
When MkDocs is the better choice
Material for MkDocs is beautiful, Python-native, trivial to run, and — since 9.7.0 folded every previously sponsor-only feature into the free MIT release — more capable at zero cost than it has ever been. For a static, offline-capable docs site built from a docs/ folder, with mkdocstrings pulling API reference out of your docstrings, it is still a great choice, and MkDocs core is maintained separately.
Frequently asked questions
Is tela a good MkDocs alternative?
Yes. No build, no deploy, no CI job — a page is live the moment you save it. tela is open-source (AGPL-3.0), self-hostable, and markdown-native, with a built-in MCP server so AI agents read and write your docs.
Can I self-host tela and connect AI agents to it?
Yes. Self-host tela for free (AGPL-3.0) or start on the free cloud tier. Its built-in MCP server lets agents like Claude search, read and write your wiki directly, on tools scoped by the token you give them.
When is MkDocs the better choice?
Material for MkDocs is beautiful, Python-native, trivial to run, and — since 9.7.0 folded every previously sponsor-only feature into the free MIT release — more capable at zero cost than it has ever been. For a static, offline-capable docs site built from a docs/ folder, with mkdocstrings pulling API reference out of your docstrings, it is still a great choice, and MkDocs core is maintained separately.
Try tela
tela is an open-source (AGPL), self-hostable team wiki. Self-host it, or start on the free cloud tier at telawiki.com. See the MCP server docs for connecting your agents, or compare tela with other tools.
mkdocs.org deployment docs; squidfunk.github.io/mkdocs-material — search setup, MIT license and the 2025-11-11 maintenance-mode announcement (verified 2026). tela facts current as of September 9, 2026.