folio-wiki

Working with Folio

Folio is a team wiki backed by Git. People edit pages in the browser. You read and write the same pages through the Folio MCP server. Your client may show the tools with a prefix, for example mcp__folio__search_pages; the names below are the server's own. Everything you write lands in Git history under the name of the token's owner, so it can be reviewed and reverted.

Order of work

1. Find. Use search_pages (it searches every space you can see when space is omitted) or list_tree for one space. Never invent a page id. If the user gave a Folio link, call resolve_folio_url first. A link like /s/<space> without /p/ is the space's home page, not the whole space.
2. Read. read_page before any edit. For a data table, folio_table_schema first, then folio_table_query.
3. Change as little as possible. Edit the part that needs changing instead of rewriting the page, unless a rewrite was asked for.
4. Re-read what you changed, then tell the user. Finish with a link to each page you created or changed: [title](/s/<space>/p/<id>), with space and id taken from the tool's reply.

Write only when the user asked for a change in the current message. Reading is always fine.

Tools

Reading: list_spaces, list_tree, search_pages, read_page, resolve_folio_url, get_backlinks, page_history, page_at_sha, folio_table_list, folio_table_schema, folio_table_query. search and fetch are read-only aliases made for ChatGPT's deep research. Prefer search_pages and read_page unless your client asks for search and fetch.

Writing (needs a token with the write scope): create_page, update_page, create_board, update_board, board_ops, folio_table_create, folio_table_add_column, folio_table_insert, folio_table_update, folio_table_delete.

If a write tool is refused, the token is read-only. Say so. Do not look for a workaround.

Pages

• A page's title is the first # H1 of its text. To rename a page, change that heading with update_page.
• create_page takes markdown for a document. If the text does not start with an H1, the server adds # <title> above it. Check the title in the reply.
• update_page works for documents only, not for tables or boards. It merges with live editing instead of overwriting someone's open session.
• Do not write front matter (id, slug, order, icon, cover) by hand. The server owns it.
• Use plain Markdown that also reads well on GitHub: headings, lists, GFM tables, fenced code, > [!NOTE] alerts, Mermaid in fenced blocks. Avoid HTML. Link other Folio pages with relative links taken from the tools' replies, not absolute URLs to the instance.
• A new page goes where the user said. If they did not say, create it under the page you are working from, or ask.