Connect Claude to Folio
To connect Claude to Folio over MCP, open Customize, then Connectors in claude.ai or Claude Desktop, click Add custom connector and paste your Folio's /mcp address. Click Connect, sign in to Folio with OAuth and choose read, or read and write. Claude then acts with your rights and nothing more. Folio must be reachable over HTTPS from the public internet.
Updated
A question and a write-back
Ask:
What is our refund process? Give me the link to the page. Then add the notes from today's Product sync as a new page under Meetings, and put the three action items in the Actions table.
Claude searches the wiki, reads the page and answers with its link. The notes appear as a page in the tree, the action items as rows in the table, and the Git history shows the commit under your name.
Connect
What you need
- A Folio instance reachable over HTTPS from the public internet. Anthropic's servers make the requests, not your computer, so localhost does not work.
- PUBLIC_URL set to that address on the Folio side. Folio builds its OAuth metadata from it.
- A Claude plan that offers custom connectors. Anthropic's help page lists Free (one connector), Pro, Max, Team and Enterprise, as of 6 October 2026.
- A Folio account. Folio has no self-registration, so an administrator invites you.
Steps
Step 1: Check that your Folio answers the way an OAuth client expects. An unauthenticated request must get a 401 with a WWW-Authenticate header that points to the metadata.
bashcurl -si -X POST https://your-folio.example.com/mcp \ -H 'content-type: application/json' -d '{}' | head -8Step 2: In Claude on the web or in Claude Desktop, open Customize, then Connectors. Click the plus, then Add custom connector. On Team and Enterprise an Owner adds it under Organization settings, Connectors, Add, Custom, Web. Name it Folio and paste the address.
Remote MCP server URLhttps://your-folio.example.com/mcpStep 3: Leave the OAuth client settings on their defaults. Folio accepts Dynamic Client Registration and client ID metadata documents, so you do not need a client ID or a secret.
Step 4: Click Connect. Folio opens its sign-in page, then a consent screen that names the app, where you will be sent back to, and whether it may also write. Choose read to start. Allow.
Step 5: Turn the Folio connector on in a chat and ask a question. Claude Desktop uses the same Connectors page: a remote connector added to your account connects from Anthropic's servers, so the claude_desktop_config.json file is not involved.
Try it against the demo
Use the same flow with https://demo.foliowiki.online/mcp. On Folio's sign-in screen pick Sam. Start with read, and ask: "Find the Release process page and tell me which checklist items are still open."
https://demo.foliowiki.online/mcpOpen the prefilled Add custom connector form
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.
What the agent can do
Folio exposes 49 tools over MCP. Full reference.
| Reading (23) | What it does |
|---|---|
list_spaces | Spaces you can see, with your role in each |
list_tree | The page tree of a space |
list_templates | The page templates of a space |
search_pages | Full-text search across the pages you can open, with filters |
read_page | A page as Markdown, with its metadata; a form's fields, a canvas's outline, a base's YAML |
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 |
get_page_metadata | A page's headings, block ids, tags, properties and links |
list_unresolved_links | Links in a space that point at nothing |
list_orphans | Pages in a space that nothing links to |
get_graph | The link graph of a space, or the neighbourhood of one page |
list_tags | The tag tree of a space with page counts |
list_properties | The property keys in use, with their types and sample values |
query_base | The rows of an Obsidian base view |
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 |
check_page_writing_rules | The space's writing rules and a page's text, so the agent can check the page against them; nothing is changed |
list_comments | The inline comment threads of a page, with the text each is attached to and its status |
| Writing (26) | 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_page_from_template | A new page copied from a template, with date, author and title filled in |
save_page_as_template | Copy an existing page into the templates of its space |
create_template | A new page template in the space's templates folder |
publish_artifact | An interactive HTML page, such as a Claude artifact, published as a page |
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 |
convert_canvas_to_board | An editable whiteboard made from an Obsidian canvas |
create_form | A form with its fields, and the table its answers go to |
update_form | Change a form's fields; the paired table follows |
folio_table_create | A table with an explicit schema |
folio_table_add_column | A new column |
folio_table_update_column | Rename a column or change its type or options |
folio_table_delete_column | A column and its values |
folio_table_save_view | A saved view with its filter, sort and hidden columns |
folio_table_delete_view | A saved view |
folio_table_insert | New rows |
folio_table_update | Cells, by row id or by filter |
folio_table_delete | Rows, by id |
rename_tag | Rename a tag across a space, in one commit |
set_page_properties | A page's properties, for any kind of page |
save_base | Create an Obsidian base or replace its YAML |
add_comment | A new inline comment thread on a passage of a page |
reply_comment | A reply in an existing comment thread |
- Reading needs the read scope. Writing needs write. With read only, every tool that changes something refuses to run.
- All 49 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.
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.
- 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
- claude.ai has no field for a personal access token. A static token works only where Anthropic has enabled custom request headers, which it offers to a limited set of organizations.
- Folio is not listed in Anthropic's connector directory. You add it by its address.
- A connection is per Folio user. Everyone in a team connects with their own account and sees what that account may see.
Read more
Frequently asked questions
How do I connect Claude Desktop to Folio as an MCP server?
In Claude Desktop open Customize, then Connectors, click the plus, choose Add custom connector, name it Folio and paste your /mcp address. Then click Connect and sign in to Folio with OAuth. Claude Desktop is the same as claude.ai here: a remote connector is added to your account, not to a file on your computer.
Do I edit claude_desktop_config.json for Folio?
No. Anthropic describes that file as a separate mechanism for local MCP servers; remote connectors are configured under Customize, Connectors. Folio is a remote server, so add it there. See Anthropic's help article.
Why does Claude say it cannot reach my Folio?
Anthropic's servers make the request, not your computer, so Folio must answer over HTTPS on the public internet, and PUBLIC_URL must be set to that address. A localhost or private-network Folio does not work with claude.ai or Claude Desktop. Claude Code, which runs on your machine, can reach a private one.
Can Claude write to my wiki, or only read it?
Both. On the consent screen you choose read, or read and write. With read only, every tool that changes something refuses to run. Writes are saved to Git history under your name.
Can Claude use a personal access token instead of OAuth?
Not in the connector form: claude.ai has no field for a token. For a token, use Claude Code. A static header in a connector works only where Anthropic has enabled custom request headers for an organization.