Skip to content

MegaMem MCP v1.7.5

Choose a tag to compare

View all tags
@C-Bjorn C-Bjorn released this 16 Jul 21:16
· 1 commit to main since this release
v1.7.5
4df0cad

MegaMem MCP v1.7.5

Installation

For Obsidian Plugin:

  1. Download the attached megamem-mcp-1.7.5.zip
  2. Extract to your vault .obsidian/plugins/megamem-mcp/ folder
  3. Reload Obsidian and enable the plugin

What is Included:

  • Main plugin files (main.js, manifest.json, styles.css)
  • Built-in MCP server for Claude Desktop integration
  • Graphiti bridge for knowledge graph functionality
  • Complete documentation site for GitHub Pages

Changes

New Features

  • Native Template Engine (Day77.01) — create_note_with_template now resolves templates from an ordered list of configured source vaults/folders (personal + company precedence, optional per-call template_source override) and renders the honest <% %> subset natively — Templater is no longer required in the target vault, enabling headless/agent-vault note creation. Registry mode (auto-detected Template-Registry Base or plain-file folder) enriches responses with whenToUse/category; a no-confident-match request returns a ranked, registry-enriched candidates list instead of guessing or erroring. Folder routing gains an in-template tp.file.move tier alongside the existing Templater settings mapping and Periodic Notes tiers. A Templater interop guard auto-manages the "ignore folders on creation" list to prevent template-syntax corruption on raw template-file writes. CLI transport only — the WebSocket path is unaffected, frozen as legacy for pre-1.12.4 Obsidian clients.

Bug Fixes

  • Cross-vault template-source home-vault resolution — a template source's empty vault_id ("use current") was resolving against the target vault being written to instead of the home vault where plugin settings and templates actually live, defeating cross-vault resolution entirely when writing to a second vault.
  • Registry-enrichment timeouts (60-80s) — the original registry lookup read every .md file in every configured source's registry folder on every call; replaced with a Base-query-first, single-file-guess-fallback strategy scoped to only the matched candidate(s).
  • Registry Base discovery — folder-adjacency heuristic replaced with filter-introspection — the old <parent-of-templates-folder>/Bases/TemplateRegistry.base path assumption didn't hold for every vault layout; discovery now enumerates .base files and matches by filter-text substring against the registry folder, with a conventionally-named-base fast path. A follow-up fix hardened that fast path so a name match must also pass the filter-text check before being accepted (a vault can carry more than one identically-named registry Base, e.g. one per source) — and extended the same targeted single-file fallback the confident-match path already had to the no-confident-match candidate list, so both paths enrich a source identically instead of the candidate-return path silently missing coverage the confident-match path had.
Assets 8
Loading