A clean workspace for your team's knowledge: familiar folders, an editor without friction – and underneath, plain Markdown files in Git, versioned automatically and open to your AI agents through a native MCP server.
No terminal needed to writeNo database lock-inFree, AGPL-3.0
Two worlds, one workspace
No more choosing between simple and powerful
Most documentation tools force a compromise: a developer platform with a steep learning curve, or a cloud app that keeps your data in its own database and locks AI tools out. Kaveyl Wiki brings both sides together – the same files, three ways in.
For everyday users
Nested folders, a clean editor that shows formatting as you type, drag and drop, templates, tags and instant search. Nobody needs to know Git – saving is automatic.
For developers & tech teams
Every page is a Markdown file in a Git repository or folder. Edit the same files in VS Code, Neovim or with git; your pull requests and CI stay exactly where they are.
For AI agents & automation
A native Model Context Protocol (MCP) server and a REST API: Claude Code, Cursor, VS Code, Claude Desktop or your own agent read, search and update the wiki – with exactly the permissions of the person behind the token.
How it works
Git does the work – invisibly
You write; Kaveyl Wiki saves at once and turns your changes into commits, with you as the author. Changes made elsewhere – in an editor, by a script or an agent – come back the same way. Nothing is ever overwritten silently.
Each source can also be a plain folder on the server – with or without its own Git repository.
GiteaGitHubGitLabAny Git URLFolders on the serverAs many sources as you like
Working together
Many people, one wiki – nothing lost
Kaveyl Wiki is not a live co-typing editor like a shared online document. It works the way Git works – which means every change is kept and traceable.
See who is there. “Maria Chen is editing” shows up as soon as someone else types in the same note.
Different places merge by themselves. Edits to different notes or different parts of a note fit together without anyone noticing.
The same place becomes a conflict, not a loss. All three versions side by side – keep yours, take theirs or combine both.
Every change has a name. Version history per note with differences, “Restore” and “Save as …”.
Permissions that fit teams. Per source, folder and note; groups, guests, invitations and sharing by e-mail.
Someone else is typing in the same noteEvery change, with author and difference
AI & MCP
Documentation that agents can read – and fix
Connect any MCP client to your wiki in a minute. Agents search, read and write notes through tools; scripts use the REST API with an OpenAPI description. Every write is a Git commit with a name on it – review it, keep it or restore the previous version.
A runbook that repairs itself
An agent sets up a server by following a guide from the wiki. Step 4 fails because a package was renamed. It finds the new name, finishes the setup and corrects the page through MCP. The commit carries the name of the person behind the token, the log marks it as MCP – and you see the exact difference in the version history.
Docs that move with the code
Claude Code changes a service and its documentation in the same repository. Kaveyl Wiki picks up the push via webhook and shows the new page to the whole team within seconds – no copying, no second system.
Built this way
Kaveyl Wiki itself was developed in exactly this loop: AI agents and a human working on the same Markdown, Git as the single source of truth.
Native MCP server
Tools to search, read, create, move and update notes, look into their history and upload files. Works with Claude Code, Cursor, VS Code, LM Studio and – through a small bridge – Claude Desktop.
REST API with OpenAPI
Everything a script needs, described at /api/v1/openapi.json. Personal tokens with read, write, MCP or manage permission and an expiry date.
An assistant that only suggests
The built-in AI (Ollama, Ollama Cloud or any OpenAI-compatible provider) helps you write and answers questions from the notes you share with it. It proposes – you decide.
One token per tool – never more rights than the person behind it
In practice
One wiki, seen from both sides
The same notes, whether you click or code.
Everyday user
Developer & AI agent
Structure
Folders with drag and drop
A plain directory tree in the repository
Writing
Editor in the browser, formatting as you type
VS Code, Neovim, git, MCP or REST API
History
Versions per note, one click to restore
Git commits and diffs, with names
AI
Ask the assistant about your notes
MCP tools for search, read and write
Storage
Your own server – nothing in someone else's cloud
Markdown in Git, or a folder on the server
Features
Everything a team wiki needs
No plugins to hunt for – it is all in the box.
Writing
Editor or Markdown source, one click apart
Tables, task lists, callouts, footnotes
Formulas (KaTeX) and diagrams (Mermaid)
Drawings with Excalidraw, images and files
Templates, tags, emoji, slash commands
Finding
Instant search across all sources
Command palette (Ctrl+K) for notes and actions
Search page with filters by tag, source and date
Backlinks: “Linked from”
Favourites and recently changed notes
Protection
Version history and trash for every note
Encrypted notes and folders
Backups to a folder or an SMB share, optionally encrypted
Restore by comparing, section by section
Nightly consistency check, links repaired on rename
People
Permissions per source, folder and note, shown as a grid
Groups, guests, invitations
Share notes, folders or sources by e-mail
Sign-in through Cloudflare Access or Authentik
Activity log for admins
Operations
One Docker container, set up in minutes
Notifications by e-mail or Pushover
Hint when a new version is out
Works behind any reverse proxy with HTTPS
Export as HTML, Markdown or PDF
Everywhere
Runs in any modern browser
Installs as an app on phone, tablet and computer
Light and dark mode
Interface and manual in English and German
Built-in manual (F1) with search
Diagrams written as textPermissions as a gridFind anything with Ctrl+K
Dark modeOn the phone, as an installed app
Self-hosted & free
Your server, your files, no subscription
Kaveyl Wiki runs as a single Docker container on a Linux server or NAS. Your notes stay plain files – take them with you any time.
Free software under the GNU Affero General Public License v3.0.
No telemetry, no tracking. Kaveyl Wiki talks to the services you connect yourself – plus an optional daily check for new versions.
Zero lock-in. Markdown files in Git or folders – readable without Kaveyl Wiki.
# folders for config, data, notes and backups
$ mkdir -p kaveyl-wiki/{config,data,docs,backup}
$ docker compose up -d
$ docker logs kaveyl-wiki # one-time setup code
# then open http://localhost:8093
Coming soon
Kaveyl Wiki is in its final round of testing. The source code, the container image and the full documentation will be published here soon.
Kaveyl
