Connect VS Code and Copilot to Folio
To connect VS Code to Folio, create .vscode/mcp.json with an http server for your Folio's /mcp address and a promptString input for the token. Start the server from the Start code lens, enter the token once, and switch Copilot chat to agent mode. Copilot can then read your team wiki and write to it.
Updated
Ask the wiki from the editor
Ask:
Search Folio for our incident response runbook and summarize the first three steps. Link the page.
In agent mode, Copilot calls search_pages and read_page, then answers with the steps and a link to the page.
Connect
What you need
- VS Code with GitHub Copilot chat in agent mode.
- A Folio token, created under the user menu, then API tokens.
- On Copilot Business and Enterprise, an organization policy for MCP servers may be off by default. If the tools do not appear, ask your administrator.
Steps
Step 1: Create .vscode/mcp.json in the workspace. The input asks for the token once and masks it.
.vscode/mcp.json{ "inputs": [ { "type": "promptString", "id": "folio-token", "description": "Folio personal access token", "password": true } ], "servers": { "folio": { "type": "http", "url": "https://your-folio.example.com/mcp", "headers": { "Authorization": "Bearer ${input:folio-token}" } } } }Step 2: Start the server from the Start code lens above its entry in the file, or run MCP: List Servers from the Command Palette. Enter the token when VS Code asks.
Step 3: Open Copilot chat, switch to agent mode and check that the Folio tools are in the tools list. Ask your question.
Try it against the demo
The demo does not issue personal tokens, so this route cannot be tried against it. Use your own Folio, or try the demo from Claude or ChatGPT.
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
- 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
- This page covers the token route. Use a token with VS Code.
- A one-click install link is not offered here, because VS Code's documentation does not specify the link format.
Read more
Frequently asked questions
How do I add an MCP server to VS Code?
Create .vscode/mcp.json with a servers entry of type http and your /mcp address. Start it from the Start code lens or run MCP: List Servers from the Command Palette. Then use Copilot chat in agent mode.
How does VS Code keep my Folio token out of the repository?
The config declares a promptString input with password: true and refers to it as ${input:folio-token}. VS Code asks for the token once and does not write it into the file.
Can GitHub Copilot in VS Code use my wiki?
Yes, in agent mode, once the Folio server is running and its tools are enabled. On Copilot Business and Enterprise an organization policy for MCP servers may be off by default; ask your administrator if the tools do not appear.