vigil.wiki·Vigil Wiki MCP server

Vigil·Updated Sep 25, 2026·vigil.wiki/notes/mcp

Vigil Wiki MCP server

Last updated: September 25, 2026

Vigil Wiki runs a Model Context Protocol (MCP) server so that AI clients such as Claude, ChatGPT, and other MCP-compatible agents can work with your notes. Once you connect a client and approve access, it can list, search, and read your notes, create and edit them, organize them into groups, and publish or unpublish them, depending on the permissions you grant.

Endpoint

Connecting a client

  1. In your AI client, add a custom connector (or remote MCP server) with the URL https://mcp.vigil.wiki/mcp.
  2. The client opens a Vigil Wiki consent page. Sign in with your vigil.center account, the single sign-in shared by the vigil apps.
  3. Review the permissions the client is asking for and approve them.

The client can then call the tools listed below on your behalf.

Authentication and scopes

The server uses OAuth 2.0 with dynamic client registration and PKCE (S256). Clients register themselves, send you to the consent page on vigil.wiki, and receive an access token bound to this server. No password or API key is ever pasted into the AI client.

ScopeWhat it allows
notes:readList, search, and read notes, groups, backlinks, templates, and published notes
notes:writeCreate and update notes, create groups, add or remove evidence references, and archive notes
notes:publishPublish a note to the public web at https://vigil.wiki/notes/<slug>/, or unpublish it

Private notes

Notes that are not published are private. By default, connected clients cannot read private notes. You can allow it under Settings → Connections (https://vigil.wiki/settings/connections) with the private-note access toggle, and switch it off again at any time.

Revoking access

The same Connections page lists every connected client. Revoking a connection cuts off that client immediately. You can also remove the connector in the AI client's own settings.

Tools

ToolScopeWhat it does
vigil_list_notesnotes:readList your notes, filtered by group, tag, or published state, with pagination
vigil_get_notenotes:readRead one note: full markdown, backlinks, and evidence references
vigil_debug_note_visibilitynotes:readExplain why a note is or is not readable (missing, private, archived)
vigil_search_notesnotes:readKeyword search across your notes
vigil_list_groupsnotes:readList your notebook groups (folders) with note counts
vigil_list_templatesnotes:readList the structured note templates (decision log, meeting note, and others)
vigil_export_contextnotes:readBundle selected notes into one markdown context pack (up to 25 notes)
vigil_get_backlinksnotes:readFind the notes that link to a given note
vigil_get_public_notenotes:readRead a published note by its public slug
vigil_create_notenotes:writeCreate a note, optionally seeded from a template. New notes start unpublished
vigil_update_notenotes:writeChange a note's markdown, title, tags, group, or slug
vigil_add_evidencenotes:writeAttach a source reference (URL, file, email) to a note
vigil_remove_evidencenotes:writeRemove a source reference from a note
vigil_archive_notenotes:writeArchive a note. This is reversible and deletes nothing
vigil_create_groupnotes:writeCreate a notebook group
vigil_publish_notenotes:publishPublish a note as a public page, or refresh its public copy
vigil_unpublish_notenotes:publishRemove a note's public page

There is no MCP tool for permanent deletion. Deleting a note for good is only possible in the vigil.wiki app.

Publishing

Publishing is a public action. A published note can be read by anyone with the URL, may be indexed by search engines, and may also appear on vigil.directory. Unpublishing removes the page from vigil.wiki, but it cannot remove copies that others have already made. The server marks the publish and unpublish tools as actions that reach the public web, so a well-behaved client asks you before running them.

Data handling

More information

helpmcp