$ loading_
Store durable memory in a GitHub-hosted Obsidian vault via markdown tools.
This MCP tool claims to let the model list, read, and append Markdown memory files in an Obsidian vault on GitHub; however, that description is materially inconsistent with the stated 'no remote endpoint' and 'no credentials', so it warrants caution. Overall, it appears to be an open-source third-party tool with file access and possible remote repository interaction, with the main concerns being insufficient disclosure and low supply-chain maturity.
The materials state that no keys or environment variables are required, but the functionality is described as operating 'on GitHub'; if it truly accesses GitHub, credentials or preconfigured authorization would normally be involved, so the credential model is insufficiently disclosed.
The system fields say there is no remote endpoint, yet the description explicitly mentions a GitHub-backed vault, implying possible network egress of user memory content to GitHub; the materials do not clearly disclose the actual hosts, data scope, or whether this behavior can be disabled.
The tool is flagged as executes-code, which means it runs code or processes locally; this is a normal MCP capability, but without a README it is unclear which system commands or subprocesses are actually invoked.
By description, it can list, read, and append Markdown files, so it at minimum has read/write access to memory content; the materials do not confirm whether access is strictly scoped to the intended vault/repository or could extend to broader file paths.
A positive factor is that it is open source and in principle auditable; however, it comes from a third-party registry, has no declared license, 0 stars, unknown maintenance status, and almost no documentation, so its supply-chain maturity and verifiability are limited.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "clawmemory-mcp" yet — see the docs or source repo.
Append today's conclusions about the MCP integration approach to the project note in the Obsidian vault, keep a timestamp, and use Markdown bullet format.
The tool appends timestamped conclusions to the target Markdown note and returns the write result.
List the Markdown files related to customer interviews in the vault, then read the two most recently updated ones and summarize them for me.
The tool lists relevant files, reads the selected notes, and produces a concise summary.
Organize my preferred writing style, common terms, and banned phrases, then save them into a long-term memory file for future reuse.
The tool creates or appends a structured preference note for durable reuse in future tasks.
Give Claude persistent memory and shared context using plain Markdown files.
Add per-repo persistent memory with versioned retrieval for Claude Code.
Lets AI retain conversation memory for more consistent long-term collaboration.
Search and filter Claude Code memory files to retrieve relevant context fast.
Give Claude Code persistent cross-session memory for project context and preferences.
Persist Claude Code conversations and retrieve relevant context across sessions.