Command Palette

Search for a command to run...

UnylyUnyly
▸ vault flow

How to use Vault with Claude

Stop writing notes by hand. Just chat with Claude as usual — your Vault assembles itself.

The 60-second setup

curl -fsSL https://unyly.org/install | sh -s -- install unyly-vault
  1. The CLI installs and detects your IDEs
  2. Browser opens — click Approve on the device-flow page
  3. Token + config written to Claude Desktop, Cursor, Claude Code automatically
  4. Restart your IDE

That's it. You never copy a token. You never edit JSON. From now on Claude has 6 tools on your personal Vault.

Capture — "remember this"

Tell Claude any thought, in plain language. Examples that all work:

  • Remember that the postgres connection string lives in 1Password under infra/db.
  • I just figured out why our build fails on Mondays — let's save this.
  • Note: customer asked for a CSV export feature, deadline Friday.
  • Quick thought: what if we cached MCP installs at the CDN edge?

Claude calls vault_create. The memory shows up in your brain graph within a second, tagged automatically based on content.

Recall — "what did I know about X?"

Days, weeks, months later — Claude searches your own memory before answering. No more "wait, where did I write that".

  • What did I learn about postgres last month?
  • Find every memory where I mentioned the gmail MCP.
  • Did I already write about edge caching?
  • Pull up my notes on the customer CSV request.

Claude calls vault_search + vault_list, shows exact quotes with dates, and follows wiki-links between notes to give you the full thread.

Connect — let Claude rewire your thinking

Each new memory automatically gets [[wiki-links]] and [[mcp:slug]] tags. Open /vault — you'll see a force-directed graph of your ideas, organic clusters by topic, MCP nodes you've referenced. The map of your thinking, growing in real time.

10 advanced prompts to copy

  1. Save this conversation as a memory titled "sprint planning · Q2".
  2. Update my note about postgres backups — add this new step at the end.
  3. What were the 3 most-mentioned topics in my Vault this week?
  4. Find memories with the #idea tag and summarise them as bullets.
  5. Show me every note that links to [[today]].
  6. Pin all my memories about the Q2 launch.
  7. What was I working on exactly one month ago?
  8. Find memories where I disagreed with myself — opposing claims about the same thing.
  9. Make this memory public — I want to share it.
  10. Pull all memories tagged #postgres, then write a summary that ties them together.

Privacy

Everything is private by default. The token only authorises Claude to access yourVault, not anyone else's. The MCP server runs on our infrastructure — no logs of contents, only access timestamps for security.

At /vault/settings you can:

  • Set Vault privacy: Public · Unlisted · Private (master switch)
  • Toggle whether your public notes appear on MCP pages (reverse mention)
  • Turn off auto-note on unyly install
  • Turn off the daily/weekly digest cron
  • Revoke the CLI token at any time

The hand-written escape hatch

Sometimes you want to write yourself — long-form, structured, with formatting. Open /vault/list, hit + new note. Markdown editor with auto-save, wiki-links autocomplete, sidebar suggestions. Same data, same graph, just typed instead of spoken.

What Claude actually gets

The MCP server exposes 6 tools — Claude picks the right one based on what you ask:

  • vault_search — full-text query across your notes
  • vault_list — list with filters (tag, pinned, favorite, daily)
  • vault_get — fetch a specific note by slug + its backlinks
  • vault_create — add a new memory
  • vault_update — edit existing memory
  • vault_backlinks — "who links to this"

Spec is MCP 2024-11-05.