anchor-notes-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANCHOR_URL | No | The URL of your Anchor instance. | |
| ANCHOR_TOKEN | No | Your Anchor API token. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Anchor is the user's notes app. Use these tools whenever they mention their notes, Anchor, or ask to note/remember/write something down.
Start with search_notes: without
searchit lists recent notes, and every result already includes the note content as markdown (cut at 1500 chars, marked truncated). Only call get_note for a truncated note or before update_note. Use scope "archived" or "trash" to look there.Search is plain substring matching, not semantic: use one short distinctive word. If nothing matches, the result includes recent notes, so you rarely need a second search.
To add to a note use append_to_note; use update_note (with the version from get_note) only to rewrite or remove text. Every edit is kept in the note's history (list_note_versions / restore_note_version), so a bad edit can be undone.
Content is markdown; titles go in
title, not as a heading in the content.Attachments (images and audio) live outside the note text: list_attachments, get_attachment (shows images to you), add_attachment (from a local file).
Notes can't be deleted permanently from here: trash_note moves them to the trash (restore_note brings them back).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_notesA | List (no |
| get_noteA | 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. |
| create_noteB | Create a note. Put the title in |
| update_noteA | Change a note. |
| append_to_noteB | Add markdown to the end of a note without touching its existing content or formatting. |
| 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. |
| restore_noteB | Bring a note back from the trash. |
| bulk_update_notesA | Apply one action to many notes at once: trash, archive, pin, unpin, or add_tags (adds |
| list_note_versionsA | List a note's saved versions, newest first (every edit, restore and conflict is kept). |
| get_note_versionB | Read one saved version of a note as markdown. |
| 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. |
| list_attachmentsB | List a note's attachments (images and audio). |
| get_attachmentA | 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 |
| add_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). |
| delete_attachmentB | Permanently delete an attachment from a note (the file is removed from the server; this cannot be undone). |
| find_usersB | Find Anchor users on this server by name or email (to share a note with them). |
| list_sharesC | List who a note is shared with. |
| share_noteB | Share a note with another user of this Anchor server, or change their permission if already shared. |
| unshare_noteC | Stop sharing a note with someone. |
| list_tagsA | List tags (id, name, color). |
| create_tagC | Create a tag. |
| update_tagC | Rename a tag or change its color. |
| delete_tagB | Delete a tag. Notes keep existing; they just lose this tag. |
| export_notesA | Download a zip backup of all the user's notes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.