Skip to content
ExoVault

Search Documentation

Search across all documentation pages

Notes & Folders

ExoVault notes are encrypted documents that agents and humans can create, edit, and search. Notes support rich markdown, wiki-links for cross-referencing, tags for categorization, and folder-based organization.

Creating Notes#

Use create_note to write a new note:

json
{
  "vaultId": "vault-uuid",
  "title": "Authentication Design",
  "content": "# Auth Architecture\n\nUsing JWT with refresh tokens. See [[API Design]] for endpoint details.",
  "tags": ["architecture", "auth", "jwt"]
}

Notes are encrypted client-side with AES-256-GCM before reaching the server. The title, content, and tags are all encrypted independently.

Updating Notes#

Use update_note to modify an existing note's content, title, or tags:

json
{
  "noteId": "note-uuid",
  "content": "Updated content with new details about OAuth2 integration."
}

You can update the title, content, and tags independently -- only the fields you provide are changed.

Deleting Notes#

Use delete_note to permanently remove a note:

json
{
  "noteId": "note-uuid"
}

Warning: Deletion is permanent. Consider archiving or moving notes to a "Trash" folder instead for important content.

Searching Notes#

Use search_notes for keyword-based search across note titles, content, and tags:

json
{
  "query": "authentication JWT",
  "vaultId": "vault-uuid",
  "limit": 10
}

For semantic search (meaning-based rather than keyword-based), use semantic_search or search_and_read. See Search Strategies for guidance on which tool to use.

Listing Notes#

Use list_notes to browse all notes, optionally filtered by vault or folder:

json
{
  "vaultId": "vault-uuid",
  "folderId": "folder-uuid",
  "limit": 50
}

Folder Organization#

Organize notes into folders for structure. Use create_folder to make new folders and list_folders to browse them:

json
{
  "vaultId": "vault-uuid",
  "name": "Architecture Decisions",
  "parentFolderId": "parent-folder-uuid"
}

Folders can be nested to create hierarchies like:

Project Alpha/
  Architecture Decisions/
    Auth Design
    Database Schema
  Meeting Notes/
    Sprint 12 Retro

Notes support [[wiki-links]] for cross-referencing. When you write [[Some Note Title]] in a note's content, ExoVault automatically:

  1. Resolves the link to a matching note by title
  2. Creates a wiki_link relation in the knowledge graph
  3. If the target note does not exist yet, creates a pending link that resolves automatically when a matching note is created later

Wiki-links work across both notes and memories, enabling a connected knowledge base.

markdown
# Sprint Planning

Based on [[Auth Architecture]] decisions, we need to implement:
- OAuth2 flow (see [[OAuth2 Implementation Plan]])
- Token refresh logic per [[Security Guidelines]]

Rich Markdown#

Note content supports full markdown including:

  • Headings, lists, and blockquotes
  • Code blocks with syntax highlighting
  • Tables
  • Links and images
  • Bold, italic, and inline code

Content is stored as HTML internally (for Tiptap editor compatibility) but you can write in plain markdown via MCP -- it is automatically converted.

Reading Notes#

Use read_note for a single note or read_notes for multiple notes by ID:

json
{
  "noteId": "note-uuid"
}
json
{
  "noteIds": ["note-uuid-1", "note-uuid-2"]
}

Next Steps#