E
evergreen-it-dev/folio
Git-backed team wiki with tables, whiteboards and live editing
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Remote endpoint (mcpServers - Claude Desktop / Cursor / Windsurf)
{
"mcpServers": {
"evergreen-it-dev-folio": {
"url": "https://demo.foliowiki.online/mcp"
}
}
}Paste this into the mcpServers config of Claude Desktop or Cursor. The endpoint comes from public evidence; we do not install or host it. Official Registry record: this endpoint lists no request headers. That is not the same as key-free - the project docs decide.
VS Code (.vscode/mcp.json - the key is servers, remote needs type: http)
{
"servers": {
"evergreen-it-dev-folio": {
"type": "http",
"url": "https://demo.foliowiki.online/mcp"
}
}
}VS Code differs from the other three: the top-level key is <code>servers</code> and a remote endpoint also needs <code>"type": "http"</code>. Paste into .vscode/mcp.json.
Claude Code (command line)
claude mcp add --transport http evergreen-it-dev-folio https://demo.foliowiki.online/mcp
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
# Folio
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
The 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.
bash
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
You own the content. Every page is a plain file in a Git repository you
control. No export step, no lock-in: stop using Folio tomorrow and the files
are still there, readable in any editor.
It works the way a wiki should. Real-time editing, a page tree, search,
access rights, history, sharing — and it keeps working offline.
Agents are first-class users. Not a chatbot bolted on the side: a
built-in assistant, your own agent in every space, a full MCP server, and
Markdown links made for agents.
Documents, tables, whiteboards, diagrams and files in one tree. A
roadmap table next to the spec, next to the architecture board, next to the
signed PDF. Obsidian canvases and bases open as pages, too, and so do the
interactive artifacts your agents make.
See how your pages connect. A graph of the space and a local graph beside
every page, built from the links your team already writes, and showing only
what the reader may open.
Built for teams. Groups, single sign-on with OpenID Connect and SAML 2.0,
SCIM provisioning, an audit log and page restrictions that child pages inherit.
Publish what should be public. Turn a space into a read-only website,
with search and an optional "Ask AI" for visitors, at a path of your
instance, on a subdomain or on your own domain.
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)
Docs as code without the IDE — the docs/ folder of a product repository becomes a space; a technical writer edits it by hand and with Folio AI, an agent adds a release entry over MCP, and the developer reads the commits with git pull (1:36)
Publish a space as a public website, with Ask AI for visitors — one setting makes a space a read-only site on a path, a subdomain or your own domain; visitors search it, download pages and ask Folio AI (1:21)
The editor and Mermaid diagrams — live Markdown, a source view of the same page, and diagrams you edit visually or as code (1:04)
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.
bash
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
You own the content. Every page is a plain file in a Git repository you
control. No export step, no lock-in: stop using Folio tomorrow and the files
are still there, readable in any editor.
It works the way a wiki should. Real-time editing, a page tree, search,
access rights, history, sharing — and it keeps working offline.
Agents are first-class users. Not a chatbot bolted on the side: a
built-in assistant, your own agent in every space, a full MCP server, and
Markdown links made for agents.
Documents, tables, whiteboards, diagrams and files in one tree. A
roadmap table next to the spec, next to the architecture board, next to the
signed PDF. Obsidian canvases and bases open as pages, too, and so do the
interactive artifacts your agents make.
See how your pages connect. A graph of the space and a local graph beside
every page, built from the links your team already writes, and showing only
what the reader may open.
Built for teams. Groups, single sign-on with OpenID Connect and SAML 2.0,
SCIM provisioning, an audit log and page restrictions that child pages inherit.
Publish what should be public. Turn a space into a read-only website,
with search and an optional "Ask AI" for visitors, at a path of your
instance, on a subdomain or on your own domain.
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)
Docs as code without the IDE — the docs/ folder of a product repository becomes a space; a technical writer edits it by hand and with Folio AI, an agent adds a release entry over MCP, and the developer reads the commits with git pull (1:36)
Publish a space as a public website, with Ask AI for visitors — one setting makes a space a read-only site on a path, a subdomain or your own domain; visitors search it, download pages and ask Folio AI (1:21)
The editor and Mermaid diagrams — live Markdown, a source view of the same page, and diagrams you edit visually or as code (1:04)
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/evergreen-it-dev-folio/)
- Source
- awesome · https://github.com/evergreen-it-dev/folio
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.