Connect your AI tools to Folio
Shared knowledge for humans and agents, backed by Git. People write pages in the browser. Agents read and write the same pages over MCP: 23 tools for search, pages, tables and whiteboards. Any client that speaks remote MCP can connect. These pages cover the ones people ask about most.
Pick your tool
Chat apps
No terminal. You add Folio by its address and sign in with OAuth.
Coding agents
Folio holds the team's conventions, decisions and plans. The agent reads them while it works.
Automation and chat interfaces
Workflows and self-hosted chat windows that call Folio with a token.
OAuth or a token
Folio supports both. The client decides which one you use.
| OAuth | Personal access token | |
|---|---|---|
| Used by | Claude, ChatGPT, and clients that can open a sign-in page | Claude Code, Cursor, VS Code, Codex, n8n, Open WebUI |
| How it works | The client opens Folio's sign-in and consent screen. You choose read, or read and write. | You create a token under API tokens and put it in the client's config as a Bearer header. |
| Whose rights | The person who signed in | The person who owns the token |
| Revoke | User menu, API tokens, Connected apps | User menu, API tokens, delete the token |
| Lifetime | One-hour access token, 30-day rotating refresh token | Until you delete it |
| Good for | People who want to use their own account in a chat | Scripts, servers and agents with their own Folio user |
The full OAuth reference is in the MCP docs.
What an agent can do
Twenty-three tools. Thirteen read, ten write. A connection never has more rights than the person behind it, and the write tools refuse to run on a read-only connection.
Ready-made config files, a Claude Code plugin, two n8n workflows and an onboarding setup are in the integrations folder of the Folio repository.
| 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) | 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 |
Try it on the demo first
Point an OAuth client at https://demo.foliowiki.online/mcp, sign in as Sam on Folio's login screen and ask about the fictional Acme handbook. The demo login is shared and its data resets every 24 hours, so a connection to it is erased with the reset. Do not connect an agent that has a shell or your own keys, and do not enter personal data. The demo does not issue personal tokens, so token clients need your own Folio.
https://demo.foliowiki.online/mcpAny other client
Folio works with any MCP client that supports remote servers over HTTP. If the client can send a custom header, use a token. If it can open a sign-in page, use OAuth. Most clients accept a config like this one.
{
"mcpServers": {
"folio": {
"url": "https://your-folio.example.com/mcp",
"headers": { "Authorization": "Bearer folio_pat_..." }
}
}
}Questions
- Can I connect ChatGPT to Folio?
- Yes, as a custom MCP server with OAuth, if your Folio is reachable over HTTPS from the public internet. Folio exposes search and fetch, so ChatGPT deep research can use it too. See the ChatGPT page.
- Can I connect Claude to Folio?
- Yes. In claude.ai or Claude Desktop, add Folio as a custom connector by its /mcp address and sign in with OAuth. Claude Code connects with a token or OAuth. See the Claude and Claude Code pages.
- Does my Folio have to be on the public internet?
- For claude.ai, Claude Desktop and ChatGPT, yes: their servers make the request, not your computer. For Claude Code, Cursor, VS Code, Codex and a self-hosted n8n or Open WebUI, the client runs on your side, so a Folio on your network is enough.
- Can an agent see pages I cannot?
- No. A connection acts with the rights of the person behind it, narrowed by the scope. A restricted page stays invisible to it.
- How do I cut an agent off?
- Delete its token under API tokens, or remove the app under Connected apps. It stops working immediately. Everything it wrote is in Git history and can be reverted.
- Is there a hosted Folio I can point Claude at?
- Only the public demo at https://demo.foliowiki.online. It is shared, resets every 24 hours and is meant for trying, not for work. For real use, run your own.