Folio MCP server

Folio

The vibe-coded, open-source alternative to Notion and Confluence. Your team's wiki lives in Git. People write in the browser, together, in real time. AI agents read and write the same pages. One command to run it yourself.

Website: · Featured in Self-Host Weekly (9 Oct 2026)

👉 Try the live demo

No install, no sign-up: open it and pick Sam on the sign-in screen. Shared login, data resets every 24 hours; don't enter personal data or API keys.

Folio was built to replace Confluence and Notion for a real team — and it was built by AI agents, in the open. The plans, specs and hand-off notes the agents work from are in this repository, next to the code they wrote. More on that below.

git clone https://github.com/evergreen-it-dev/folio.git
cd folio
docker compose up -d

Open , create the first account, start writing.

Not ready to install? Try the live demo first.

Why Folio

control. No export step, no lock-in: stop using Folio tomorrow and the files are still there, readable in any editor.

• You own the content. Every page is a plain file in a Git repository you

access rights, history, sharing — and it keeps working offline.

• It works the way a wiki should. Real-time editing, a page tree, search,

built-in assistant, your own agent in every space, a full MCP server, and Markdown links made for agents.

• Agents are first-class users. Not a chatbot bolted on the side: a

roadmap table next to the spec, next to the architecture board, next to the signed PDF.

• Documents, tables, whiteboards, diagrams and files in one tree. A

• One command to run. Docker, and nothing to configure for a first start.

See it in action

Short walkthroughs, no slides. The voice in the videos is synthetic.

• A team wiki that lives in Git — edit a page in the browser, press Sync, and it is a real Git commit; a teammate edits from the terminal and the change shows up on the page (0:37)
• An AI agent updates your wiki over MCP — one request: the agent reads the release process, writes release notes and adds a roadmap row (0:53)
• Onboarding a sales rep with Folio AI — answers from the team's own pages with sources, a weekly check as a form, and the results in a table (1:22)
• Whiteboards that live in Git — draw together, embed the board in a document, and keep every version in history (0:51)
• The editor and Mermaid diagrams — live Markdown, a source view of the same page, and diagrams you edit visually or as code (1:04)
• Is your wiki's AI assistant helping? Folio AI analytics — instance admins see rated conversations and unanswered questions, add the missing page, and the same question gets an answer with its source (1:21)

Git-first, all the way down

Most wikis keep your content in a database and offer Git as an export. Folio does the opposite: the Git repository is the wiki. The database holds the index, access rights and the state of live editing — never the only copy of your words.

This is what a space looks like on disk:

Shortened. The full README is on GitHub.