memorry

approved

by Mehmet Ali Çalapverdi

Search, filter, and browse the memory records the memorry MCP server syncs into your vault, from a dedicated sidebar pane. - This plugin has not been manually reviewed by Obsidian staff.

2 stars84 downloadsUpdated 1mo agoMIT

obsidian-memorry

An Obsidian companion plugin for memorry — a local, API-key-free MCP memory server. Adds a dedicated sidebar pane to search, filter, and browse the memory records memorry syncs into your vault.

memorry banner

What it does

The memorry sidebar pane: a search box, a project filter, a pinned section, and the record list

memorry's server already mirrors every memory record into your vault as a Markdown note (with id/project/title/tags/created_at/pinned frontmatter) and links related notes together for the Graph View. This plugin reads those notes directly and gives you:

  • A search box that filters by title, body, tags and project as you type
  • Coloured tag chips — click one to filter by it, click again to clear. Each chip carries its record count, so cluster sizes are visible at a glance
  • A project dropdown to narrow the list to one project
  • A pinned section that always surfaces your 📌 records first
  • Two-line previews so records are distinguishable without opening them
  • A live-updating list (re-scans automatically when notes change)
  • One click to open any record's underlying note

Tag colours are derived from the tag name itself, not a built-in vocabulary — your tags get stable colours whatever language you write them in.

Records written before server v0.5 have no title/tags; they still list fine, falling back to the filename with its numeric id prefix stripped.

What it doesn't do (yet)

This is read-only and vault-native — it parses frontmatter straight out of app.metadataCache, so it works even if the memorry server isn't running. It does not talk to the memorry MCP server over the network, which means:

  • No add/delete/pin-toggle from inside Obsidian (use the MCP tools, or edit frontmatter and let memorry's own sync reconcile it — not currently two-way, so this will drift; treat the vault as a mirror of the DB, not the source of truth)
  • Search is a simple substring match, not memorry's real FTS5/bm25 ranking (no Turkish suffix stripping either — the server matches yedek and yedekleri to the same records, this panel does not)

Implementing an in-plugin MCP client (streamable-http, JSON-RPC) to close that gap is the natural next step — issues/PRs welcome.

Install

Grab main.js, manifest.json, and styles.css from the latest release and drop them into <your-vault>/.obsidian/plugins/memorry/.

Then reload Obsidian (Command palette → "Reload app without saving"), enable memorry under Settings → Community plugins, and open the panel from the ribbon icon or the "Open memorry panel" command.

If you changed the server's Obsidian sync folder from its default, set the matching vault-relative folder name in the plugin's settings.

Upgrading from 0.1.0: the plugin id changed from obsidian-memorry to memorry (Obsidian's review guidelines discourage "obsidian" in plugin ids). Rename the plugin folder to memorry — or delete the old folder and install fresh — otherwise Obsidian will list it twice.

Build from source

npm install
npm run build   # type-checks with tsc, then bundles with esbuild -> main.js

License

MIT

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.