E
evergreen-it-dev/folio
Git-backed team wiki with tables, whiteboards and live editing
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
远端端点（Claude Desktop / Cursor / Windsurf 共用 mcpServers）
{
"mcpServers": {
"evergreen-it-dev-folio": {
"url": "https://demo.foliowiki.online/mcp"
}
}
}把这段粘进 Claude Desktop / Cursor 的 mcpServers 配置即可。端点来自公开证据，我们没有替你安装或托管它。 官方 Registry 记录：这个端点没有列出任何请求头。这不等于免密 —— 以项目文档为准。
VS Code（.vscode/mcp.json —— 键名是 servers，远程要 type: http）
{
"servers": {
"evergreen-it-dev-folio": {
"type": "http",
"url": "https://demo.foliowiki.online/mcp"
}
}
}VS Code 的配置文件和另外三家不同：顶层键是 <code>servers</code>，远程端点还要写 <code>"type": "http"</code>。复制到 .vscode/mcp.json。
Claude Code（命令行）
claude mcp add --transport http evergreen-it-dev-folio https://demo.foliowiki.online/mcp
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- 来源明细
- 收录自 abordage/awesome-mcp 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-11-05 · 最近见到 2026-11-14 · 共见到 10 次 · 被 10 个来源列出
- 评分构成
- 综合分 1,003 · 10 个来源 · mcp
常见问题（答案都来自我们的记录）
怎么安装？
我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。
它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
我们收录于 2026-11-05；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
# 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)
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/evergreen-it-dev-folio/)
- 来源
- awesome · https://github.com/evergreen-it-dev/folio
- 按领域浏览
- MCP 服务
- 收录来源
- 10 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。