anchor-notes-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@anchor-notes-mcp Find my note about the Q3 roadmap and append a link to the design doc"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
anchor-notes-mcp
An MCP server for Anchor, the self-hosted notes app. It lets Claude (Claude Code, Claude Desktop, or any local MCP client) search, read, create and edit your notes.
Notes go in and out as markdown, converted with Anchor's own import/export code. Headings, bold, italic, underline, strike, highlights, links, lists, checklists, quotes and code blocks all survive the round trip, so Claude's edits show up properly formatted in the app.
Install
You need Node.js 20 or newer and a running Anchor instance.
npx anchor-notes-mcp setupThe setup does four things:
Asks for your Anchor URL.
Signs you in with your email and password and fetches your API token, creating one if you don't have it yet. You can paste a token instead. Your password is never stored.
Saves the URL and token to
~/.config/anchor-notes-mcp/config.json.Offers to register the server in each Claude Code profile and in Claude Desktop it finds.
Restart Claude Desktop afterwards. To check everything:
npx anchor-notes-mcp doctorAny MCP client can start it with npx -y anchor-notes-mcp. On Windows, use cmd /c npx -y anchor-notes-mcp. It reads the config file, or the ANCHOR_URL and ANCHOR_TOKEN environment variables, which take precedence.
claude mcp add --scope user anchor -e ANCHOR_URL=https://notes.example.com -e ANCHOR_TOKEN=... -- npx -y anchor-notes-mcpRelated MCP server: Zettelkasten MCP Server
Tools
Area | Tools | What they do |
Notes |
| List or search active, archived or trashed notes; results include each note's markdown (first 1,500 chars) |
| Read and write notes as markdown, including background color and reminders | |
| Move to and back from the trash | |
| Trash, archive, pin, unpin or tag up to 200 notes at once | |
History |
| Browse and restore earlier versions; every edit is kept |
Attachments |
| Images are shown to Claude directly; audio and big files are saved to disk; upload images or audio from a local file |
Sharing |
| Share notes with other users on your server as viewer or editor |
Tags |
| Manage tags |
Backup |
| Save a zip of all notes, as markdown or in Anchor's own format |
Safe edits:
update_notesends the version Claude read. If you changed the note in the app in the meantime, Anchor rejects the write, nothing is lost, and Claude is told to re-read and retry.append_to_notenever rewrites the existing content.Every edit lands in the note's history, so a bad one can be undone with
restore_note_version.Notes are never deleted for good.
Tools that do delete something (an attachment, a tag, a share) are marked destructive, so your client can ask before running them.
Downloads never overwrite existing files.
Security
Your API token stays in the local config file and only goes to your Anchor server.
Your password is never stored.
The server can't permanently delete notes, only move them to the trash.
add_attachmentonly uploads image and audio files;get_attachmentandexport_notesonly write new files.npx -y anchor-notes-mcpalways runs the latest release. To pin a version, useanchor-notes-mcp@0.2.0in your Claude config.
See SECURITY.md for details and how to report a vulnerability.
Development
npm install
npm test # markdown round-trip fixtures from Anchor + every tool against a fake Anchor
npm run build # dist/cli.js, a single self-contained file
npm run smoke # end-to-end against your configured instance; creates and trashes a test note (--keep to inspect it)
node dist/cli.js setup --local # register this checkout instead of the npm packageLicense
AGPL-3.0. The markdown conversion in src/vendor/anchor/ and the test fixtures are copied from Anchor, which is AGPL-3.0; each file names the commit it came from.
Available Tools
24 toolsadd_attachmentA
Attach a local file to a note. Anchor accepts images and audio up to 50 MB (.jpg .jpeg .png .webp .gif .mp3 .wav .m4a .mp4 .ogg .aac .weba .webm).
Inputs: noteId (required), filePath (required).
append_to_noteB
Add markdown to the end of a note without touching its existing content or formatting.
Inputs: id (required), content (required).
bulk_update_notesA
Apply one action to many notes at once: trash, archive, pin, unpin, or add_tags (adds tagIds, keeps existing tags).
Inputs: action (required), noteIds (required), tagIds.
create_noteB
Create a note. Put the title in title, not as a heading in content.
Inputs: title (required), tagIds, content, isPinned, +2 more.
create_tagC
Create a tag.
Inputs: name (required), color.
delete_attachmentBDestructive
Permanently delete an attachment from a note (the file is removed from the server; this cannot be undone).
Inputs: noteId (required), attachmentId (required).
delete_tagBDestructive
Delete a tag. Notes keep existing; they just lose this tag.
Inputs: id (required).
export_notesARead-only
Download a zip backup of all the user's notes. markdown = readable .md files; anchor = Anchor's own format, for re-importing. Saved to disk (never overwriting); returns the path.
Inputs: format, saveTo.
find_usersBRead-only
Find Anchor users on this server by name or email (to share a note with them).
Inputs: query (required).
get_attachmentARead-only
Get an attachment. Images up to 3.5 MB are shown to you directly; audio and larger images are saved to disk (never overwriting) and the path is returned. Pass saveTo to always save.
Inputs: noteId (required), attachmentId (required), saveTo.
get_noteARead-only
Read one whole note as markdown, with its current version. Needed only for notes search_notes marked truncated, or to get the version before update_note.
Inputs: id (required).
get_note_versionBRead-only
Read one saved version of a note as markdown.
Inputs: noteId (required), versionId (required).
list_attachmentsBRead-only
List a note's attachments (images and audio).
Inputs: noteId (required).
list_note_versionsARead-only
List a note's saved versions, newest first (every edit, restore and conflict is kept).
Inputs: noteId (required), limit, cursor.
list_tagsARead-only
List tags (id, name, color).
Inputs: no named parameters.
restore_noteB
Bring a note back from the trash.
Inputs: id (required).
restore_note_versionB
Restore a note's title and content to a saved version. The current text is kept in history first, so this can be undone.
Inputs: noteId (required), versionId (required).
search_notesARead-only
List (no search) or search the user's Anchor notes. Results include each note's markdown content (first 1500 chars). If a search of active notes matches nothing, recent notes are returned instead.
Inputs: limit, scope, tagId, search.
trash_noteA
Move a note to the trash (restore_note brings it back; the trash empties itself after 30 days). On a note shared with the user, this leaves the share instead.
Inputs: id (required).
update_noteA
Change a note. content replaces the whole body, so read the note with get_note first and send the full edited markdown. To only add text at the end, use append_to_note instead.
Inputs: id (required), baseVersion (required), title, tagIds, +5 more.
update_tagC
Rename a tag or change its color.
Inputs: id (required), name, color.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 24 tools
Most tools map to a distinct resource+action, but pairs like restore_note vs restore_note_version and get_note vs get_note_version rely on descriptions to differentiate, and trash_note vs delete_attachment differ in destructiveness without naming cues. Overlap between update_note, append_to_note, and bulk_update_notes is handled well by explicit guidance in the descriptions.
Every tool follows a consistent snake_case verb_noun pattern (create_note, list_shares, restore_note_version, delete_tag). No mixed conventions or vague verbs anywhere in the set.
24 tools is at the upper edge of comfortable, but the surface spans several sub-domains (notes, versions, attachments, tags, shares, bulk ops, export) so each tool earns its place. A few could be folded together, e.g. bulk actions living only inside bulk_update_notes while single archive/pin are absent.
Strong coverage: note CRUD plus append and trash/restore, full version history, attachment lifecycle, tag CRUD, and share management, plus export. Minor gaps remain: no single-note archive/pin/unpin tool (only via bulk_update_notes), no permanent delete or empty-trash operation, and no dedicated way to list trashed notes.
Maintenance
Related MCP Connectors
Persistent memory layer for AI tools. Save and recall notes across Claude and other MCP clients.
Notes and memory assistant: one Markdown vault that Claude, ChatGPT and any MCP client can share.
Read and write your Fresh Jots notes from Claude, Cursor, and any MCP client.
MCP-native notes and memory for ChatGPT, Claude, and other AI tools.
Related MCP Servers
- FlicenseNot gradedqualityAmaintenanceEnables users to create, link, explore, search, and synthesize atomic Markdown notes through Claude and other MCP-compatible clients, with tagging, semantic link types, and dual Markdown/SQLite storage.-
- FlicenseNot gradedqualityAmaintenanceEnables users to create, link, explore, and synthesize atomic notes through Claude and other MCP-compatible clients, with markdown storage, tags, search, and semantic link types.-
- FlicenseNot gradedqualityAmaintenanceEnables users to create, link, tag, search, explore, and synthesize atomic notes through Claude and other MCP-compatible clients, using Markdown files as the source of truth and an SQLite index for fast knowledge graph traversal.-
- FlicenseNot gradedqualityAmaintenanceEnables users to create, link, search, explore, and synthesize atomic notes through Claude and other MCP-compatible clients, using Markdown files backed by a SQLite index.-