Folio MCP
A team wiki living in Git with a 51-tool MCP server: agents read and edit pages, tables and boards.
- 83 ★ on the repository
- Last commit
Extended access
Why this level
- The agent reads and edits wiki pages with the token owner rights, and without review mode edits apply immediately.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/folioDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent reads and edits wiki pages with the token owner rights, and without review mode edits apply immediately.
This is third-party code. Review the repository files before installing.
What it does
Folio is an open-source alternative to Notion and Confluence: pages live as files in a Git repository and people write together in the browser in real time. The built-in MCP server at `/mcp` gives agents 51 tools: page search and reading, writing, forms, data tables, boards, the link graph, history, comments and a check of a page against the space writing rules. Connect with a personal access token or through OAuth 2.1 from cloud clients such as Claude and ChatGPT. A space admin can switch agent edits to review mode, so changes appear as proposals with line-by-line diffs. Pages tagged `skill` with a description are served to connected agents as team skills. Any page can be fetched through a link as clean Markdown.
Who it is for. Teams that keep documentation in Git and want agents to access it with human-level rights and edit review.
Good fit when
- An agent updates a process page and adds a row to a roadmap table.
- Agent edits first go to an editor for review with a line diff.
- Team instructions live in the wiki and reach agents as skills.
- Find orphan pages and unresolved links using the space graph.
Not a fit when
- You need a ready cloud wiki with no self-hosting.
- Documentation lives outside Git and cannot be migrated.
- Agents must not get write access even in review mode.
Example request
Read the release process page, draft the release notes and add a row to the roadmap table. Send the edits for review.MCP
- Transport
- http
- Authentication
- OAuth
Environment variables
FOLIO_TOKENrequired, secret- Folio personal access token, sent in the Authorization header
Limitations
Hosting is yours: `docker compose up -d` after cloning the repository, then create the first account at `http://localhost:4870`. The built-in Folio AI assistant needs your own provider key; everything else works without it. MCP clients get the token owner rights and no more, but edits apply immediately by default; review mode is enabled in space settings and covers Markdown pages only. The live demo is shared and resets every 24 hours, so enter no personal data. The project is young, with its repository active through November 2026.
How to disable. Remove the `folio` connection from the client, revoke access tokens in your Folio profile and the connector OAuth grant. Stop the wiki itself with `docker compose down`; page files stay in Git.
FAQ
How do I connect Claude Code to Folio?
With `claude mcp add folio --transport http`, your instance `/mcp` URL and an Authorization header carrying a personal token. Claude and ChatGPT use a custom connector with OAuth.
How many tools does the MCP server have?
Fifty-one. They cover pages, data tables, boards, tags, properties, the link graph, history and comments; `search` and `fetch` support ChatGPT deep research.
Can agent edits be reviewed before they apply?
Yes. In the space menu under AI agents choose the review option: edits become proposals that an editor or admin accepts.
Where are pages stored?
Each page is a plain file in a Git repository you control. If you stop using Folio, the files remain readable in any editor.
What are team skills?
A page tagged `skill` with a `description` property is offered to agents through `list_skills`, `get_skill` and MCP prompts, so team instructions live in the wiki rather than in files on every machine.
Discussion
No questions or reviews yet.
Related
MCP serversThe MCP endpoint of a Salt workspace on your server: an agent creates pages, databases and comments with a person rights.
A personal wiki in a .wiki folder: the agent reads sources, writes cross-linked pages and health-checks the knowledge base
A self-hosted markdown wiki with a built-in MCP server: agents search, read and write pages under scoped permissions
A local wiki memory built from what you read: a shared knowledge folder for agents through an MCP bridge and my-curator.
The official Kibela MCP server searches, reads and edits notes, folders and comments of your wiki straight from an assistant chat
An agent saves web pages, PDFs and scans into a local vault, builds linked concepts and answers from them with source references.
README in short
The repository opens the Folio wiki: a Docker Compose start, a feature list, an agent section with the MCP server, ready integrations and the permission model.