markdown-memory-mcp
Related Servers
Alternatives to markdown-memory-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceExposes a Markdown vault as long-term memory for MCP-compatible LLM clients, letting agents search, read, create, update, and delete notes, manage core persona and persistent directives, append to daily logs, and inspect backlinks, tags, and the link graph. It runs locally over stdio against a chosen vault directory.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to search, read, stage candidate memories, and inspect vault status against a local Markdown-based memory vault over stdio.Apache 2.0
- AlicenseNot gradedqualityFmaintenanceExposes a stdio MCP server that indexes a markdown vault (such as an Obsidian folder of notes) into SQLite FTS5 and answers BM25-ranked section-level queries, with filters for note type. It also exposes reindexing so notes edited on disk become searchable again, giving coding agents persistent, durable memory across sessions.MIT
- AlicenseNot gradedqualityCmaintenanceExposes a local Markdown vault to AI agents over stdio, letting them search, read, create, update (with mtime-guarded writes), and append notes, as well as list and manage saved views. Write permissions can be toggled per group in settings, and all changes land as plain Markdown/YAML files in the chosen folder.MIT
- AlicenseAqualityBmaintenanceLocal MCP server for querying and maintaining a Markdown vault. Provides full-text search, backlinks, note retrieval, and optional confined write tools, without sending the whole vault to the client context.22110 PyPI1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and manage a local Markdown memory vault over stdio, including hybrid search, note retrieval and addition, session handoff claiming, and status checks without holding a model in memory.MIT
TDQS
Scored across 4 tools
Each tool targets a clearly distinct operation: semantic/keyword retrieval (search_notes), full-text retrieval by name (read_note), link-graph inspection (backlinks), and vault health checking (lint_vault). There is no overlap — search vs. read is a natural retrieve-then-expand split, and backlinks/lint are separate concerns entirely.
Three of four tools follow a clean verb_noun snake_case pattern (search_notes, read_note, lint_vault). 'backlinks' breaks the pattern as a bare noun, a minor but noticeable deviation.
Four tools is lean but each one earns its place in a read/retrieve workflow. It sits just under the comfortable range, so the surface feels slightly minimal rather than over-scoped.
The surface is read-only: there is no way to create, update, or delete a note, and no listing/enumeration of the vault. For a 'memory' server, the inability to write a memory is a significant gap that will force agents to fail on store/update workflows.