Memex
Related Servers
Alternatives to Memex
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceGit-native long-term memory for AI agents: your markdown files are the source of truth, the search index is a disposable projection rebuilt from git, and every memory the agent writes is a reviewable git commit. Served over one OAuth-secured MCP endpoint with hybrid lexical+semantic recall and a gated, git-first commit_note write tool.78AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceOpen, Git-native memory protocol for MCP agents: stores memories as Markdown files in a Git repo, enabling portability, auditability, and human-editable memory across different AI agents.103 npm15MIT
- AlicenseNot gradedqualityDmaintenanceMCP server providing persistent, local-first memory for AI agents via Markdown files in a git repo, with search, branching, and auditability.5 npm2MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first, file-based memory layer for AI agents — one shared Markdown vault across Claude, Codex, Gemini, Cursor and any MCP client. Provides read/write memory tools with an audit trail, per-agent trust levels, and Git sync; no cloud and no lock-in.2MIT
- AlicenseAqualityAmaintenanceAudit-grade, git-versioned memory for AI coding agents that enables saving, searching, editing, and rolling back facts through markdown files served via MCP.39358 PyPI46MIT
- AlicenseAqualityBmaintenanceLocal-first memory layer for AI coding agents — Markdown as source of truth, MCP server + CLI, human-reviewed capture, team knowledge via git PRs613779 npm6Apache 2.0
TDQS
Scored across 7 tools
Each tool has a distinct role: read_note (fetch full body by id) vs recall (ranked snippet search), list_notes vs list_tags (different resources), and remember (write/update) vs resolve_conflict (deliberate contradiction workflow). The descriptions explicitly cross-reference each other (recall says 'use read_note for the full text'; remember's warnings feed resolve_conflict), so an agent can pick correctly.
Four tools follow a verb_noun pattern (read_note, get_backlinks, list_notes, list_tags) and all names are uniformly snake_case. The three memory-lifecycle tools use bare verbs (remember, recall, resolve_conflict), which is a minor but readable deviation rather than inconsistency.
Seven tools is well-scoped for a personal notes/memory server, and each earns its place: read, write, search, list, list tags, backlinks, and conflict resolution. No redundant or filler tools are present.
The surface covers the full read/write/search/update lifecycle plus backlinks and explicit conflict resolution, with supersede semantics substituting for deletion. Minor gaps remain: there is no 'forget'/delete operation at all, and no way to list a note's outgoing links (only backlinks), which agents may want for graph navigation.