memorry

by Mehmet Ali Çalapverdi
5
4
3
2
1
Score: 50/100

Description

Obsidian companion plugin for memorry -- search, filter, and browse your synced AI-memory notes from a sidebar pane.

Reviews

No reviews yet.

Stats

2
stars
14
downloads
0
forks
5
days
6
days
6
days
0
total PRs
0
open PRs
0
closed PRs
0
merged PRs
0
total issues
0
open issues
0
closed issues
7
commits

Latest Version

6 days ago

Changelog

Fixes the one error the automated review raised against 0.2.2.

  • minAppVersion 1.4.0 -> 1.7.2. Workspace.revealLeaf only returns a Promise @since 1.7.2, and the plugin awaits it so a deferred view finishes loading before it's revealed. Declaring 1.7.2 is the honest fix rather than dropping the await.
  • Command id no longer repeats the plugin id, and the command name no longer repeats the plugin name -- Obsidian adds both itself.

Install: download main.js, manifest.json and styles.css below into <vault>/.obsidian/plugins/memorry/. Requires Obsidian 1.7.2 or newer.

README file from

Github

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

memorry's server already mirrors every memory record into your vault as a Markdown note (with id/project/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 and project as you type
  • A project dropdown to narrow the list to one project
  • A pinned section that always surfaces your 📌 records first
  • A live-updating list (re-scans automatically when notes change)
  • One click to open any record's underlying note

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

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