Notesnook MCP. Manage private, encrypted notes without exposing data.

Notesnook connects your agent directly to your private note vault. This isn't just another cloud storage bucket; you're dealing with zero-knowledge, end-to-end encrypted notes here. Your agent acts like an extension of your own memory, letting you interact with highly sensitive data—you never expose the raw text or payload to third parties.

You simply tell your AI client what you need, and it handles all the secure handshakes.

To get started, remember that every action runs through specialized tools. The get_user tool checks and confirms your authenticated security identity within Notesnook before anything else happens. This validates that you're who you say you are before you even check a single note.

Retrieving and Auditing Your Knowledge Base

You can start by mapping out the structure of your entire vault. The list_notebooks tool shows you the main groupings that organize everything, letting you see how you've structured your thoughts. If you want to see what concepts tie different notes together across the whole collection, run list_tags. This enumerates all cross-cutting categorical tags used for indexing.

To see what notes are stored overall, use list_notes; this returns a list of every encrypted note ID in the vault. You can narrow that down by checking out your high-priority items with list_favorites, or if you're cleaning house, you can review records of nodes marked for permanent deletion using list_trash.

When you need to read the actual content, get_note retrieves the full, underlying encrypted cipher payload for a specific note ID. You won't get plaintext—you get the sealed data. If that note has binary files attached, list_attachments shows you exactly what those attachments are; it lists all PDFs, images, or other binaries stored inside your vault.

Injecting and Modifying Content

When you have a new idea, you don't manually upload it. You use the create_note tool. It takes plaintext from your agent and pushes it into the vault’s persistent, secure storage layer, encrypting it immediately so it's safe. If an existing note needs tweaking—maybe you added some details or fixed a typo—you run update_note.

This modifies partial strings of content in that specific note and forces re-encryption across that item payload. It keeps the seal intact while letting you change the guts.

If you decide a whole entry is trash, you use delete_note. This irreversibly removes a specific encrypted note from the server and marks it for permanent erasure, so you know it’s gone for good.

Maintaining Data Integrity and State

The vault structure itself needs upkeep. If your local copy might be out of sync with the actual server data—maybe you checked notes on two different machines—you run sync_items. This triggers a full vault sync, fetching any encrypted binary objects or state changes that have happened since your last connection.

You'll know your local view matches the source of truth.

The system works by allowing granular control over every aspect: you list the structure (list_notebooks), check the metadata (list_tags), retrieve the content payload (get_note), manage attachments (list_attachments), and then push changes back through creation, modification, or deletion tools. You're in total command of your encrypted knowledge base.