Connect Claude Code to Folio

Your code sits in a repository. Your release process, decisions and roadmap sit in Folio. Claude Code can read both in one session and write back to the wiki. One command connects it.

Sign-in: Token or OAuth

Connect MCP docs

From a release to release notes in one request

Ask:

In the Acme Handbook space, find the release process page and tell me which checklist items are still open. Then create a page called "Release notes" under Engineering with a short summary of the roadmap items that are Done or In review. Then add a row to the Roadmap table: Public changelog page, status Planned, owner sam, team Design, due 2026-10-20, effort 2 days.

The agent reads the checklist, creates the page in the tree and adds the row. About a minute later the history of the page shows a normal Git commit. The same request is the one in the video.

Connect

What you need

Claude Code installed.
A Folio account. For a token, create it under the user menu, then API tokens. Scope write lets the agent edit; read is enough for questions.
Your Folio address. Claude Code runs on your machine, so a Folio on a private network works.

Steps

Step 1: Create a token named Claude Code. Better still, create it under a separate Folio user for the agent, with the editor role only in the spaces it needs.

Step 2: Add the server. Replace the address and the token.

bash

claude mcp add --transport http folio https://your-folio.example.com/mcp \
  --header "Authorization: Bearer folio_pat_..."

3
Step 3: Or install the Folio plugin from the repository. It carries the connection and a skill that tells the agent how to work with pages, tables and boards. In a session, the same two commands start with /plugin.
bash
```
claude plugin marketplace add evergreen-it-dev/folio
claude plugin install folio@folio
```
4
Step 4: For a team repository, put the connection in .mcp.json at the project root and keep the token in an environment variable, so it never reaches Git. Each person sets FOLIO_TOKEN in their shell. Use your own variable name: Claude Code blanks credential names it knows, such as ANTHROPIC_AUTH_TOKEN, in remote headers.
.mcp.json
```
{
  "mcpServers": {
    "folio": {
      "type": "http",
      "url": "${FOLIO_URL:-https://your-folio.example.com}/mcp",
      "headers": { "Authorization": "Bearer ${FOLIO_TOKEN}" }
    }
  }
}
```
bash
```
export FOLIO_TOKEN=folio_pat_...
```
5
Step 5: Check the connection. In a session, run /mcp: folio should be connected, with 23 tools. From the shell, claude mcp list shows the same.
bash
```
claude mcp list
```
6
Step 6: Prefer to sign in with your own account instead of a token? Add the server without a header, then authenticate. Folio opens its sign-in and consent screen.
bash
```
claude mcp add --transport http folio https://your-folio.example.com/mcp
claude mcp login folio
```

Try it against the demo

The demo does not issue personal tokens, so use the OAuth route: add https://demo.foliowiki.online/mcp, authenticate, and pick Sam on Folio's sign-in screen. Then ask for the open items on the Release process page.

Demo MCP address

https://demo.foliowiki.online/mcp

Step 1: Add the demo, then sign in.

bash

claude mcp add --transport http folio-demo https://demo.foliowiki.online/mcp
claude mcp login folio-demo

The demo login is shared and the data resets every 24 hours, which also removes your connection. Pages written by other visitors are untrusted data, so do not connect an agent that has a shell or your own keys, and do not enter personal data. Requests are rate limited.

Open the demo

What the agent can do

Folio exposes 23 tools over MCP. Full reference.

Reading (11)
Reading (11)	What it does
`list_spaces`	Spaces you can see, with your role in each
`list_tree`	The page tree of a space
`search_pages`	Full-text search across the pages you can open
`read_page`	A page as Markdown, with its metadata
`resolve_folio_url`	A Folio link to the page it points at
`get_backlinks`	Pages that link to a page
`page_history`	The Git commits that touched a page
`page_at_sha`	A page as it was at a given commit
`folio_table_list`	Data tables in a space
`folio_table_schema`	A table's real columns, types and options
`folio_table_query`	Table rows with filter, sort and search
`search`	The same search under the name ChatGPT deep research looks for
`fetch`	A page by the id that search returned, as Markdown

Writing (10)
Writing (10)	What it does
`create_page`	A new document with text, or a table with columns
`update_page`	Replace the text of a page; merges with live editing
`create_board`	A whiteboard from a short description of boxes and arrows
`update_board`	Replace a whiteboard's scene
`board_ops`	Align, distribute, move or auto-layout board elements
`folio_table_create`	A table with an explicit schema
`folio_table_add_column`	A new column
`folio_table_insert`	New rows
`folio_table_update`	Cells, by row id or by filter
`folio_table_delete`	Rows, by id

Reading needs the read scope. Writing needs write. With read only, every tool that changes something refuses to run.
All 23 tools carry read-only or destructive annotations, so a client can ask before it writes.
An agent cannot manage access rights, invite people, or rename and delete spaces. Those actions exist only in the browser.
A write reaches the page file at once. The Git commit follows after about 90 seconds of quiet, so page history can lag behind an edit.
Claude Code can also read your repository in the same session, so you can ask it to compare the wiki with the code: read git log since the last tag and add to the release notes what the roadmap table is missing.

Security

You sign in to your own Folio account and choose read, or read and write, on the consent screen. The connection acts with your rights and nothing more: a page you cannot open stays invisible to it.
Writes are saved to Git history under your name.
Access tokens last one hour and are renewed by a refresh token that rotates on every use. Folio stores only hashes of them.
To disconnect, open the user menu, then API tokens, then Connected apps, and remove the app. Its tokens stop working immediately. Disabling the user does the same.
An OAuth token works on /mcp only, not on the REST API.
A personal access token carries the rights of the person who created it, narrowed by its scope. Give an agent its own Folio user with the editor role in the spaces it needs, and create the token there. Do not hand an agent an administrator's token.
Use a read token when the agent only answers questions.
The token is shown once. Keep it in an environment variable or the client's secret store, not in a file that goes to Git. Delete it under API tokens when you stop using it.
Administrative routes are cookie-only: no token reaches them with any scope.
Page content is data, not instructions. Folio's tool descriptions say so, but the real protection is rights. An agent that also has a shell and write access can be misled by a page someone else wrote, so give it the narrowest token that does the job.

Limits and honest notes

If a header is set and Folio rejects it, Claude Code reports a failed connection and does not fall back to OAuth. Check the token first.
The OAuth route, claude mcp login, is from Claude Code's documentation. We have run the token route, not this one.
Claude Code may ask before each tool call, depending on your permission settings. Folio's annotations let it tell reads from writes.

Other integrations

Claude ChatGPT Cursor VS Code Codex n8n Open WebUI

All integrations