F
licenseNot graded
qualityA
maintenancePersistent memory for AI coding agents: local-first semantic search, dependency graphs, git history.
1
-
RMS Memory MCP
by max-ramas
Related Servers
Alternatives to RMS Memory MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocal-first memory layer for AI coding agents — Markdown as source of truth, MCP server + CLI, human-reviewed capture, team knowledge via git PRs6111,278 npm6Apache 2.0
- AlicenseAqualityAmaintenanceLocal-first memory for AI coding agents using SQLite, enabling persistent recall of decisions, lessons, and project context without cloud or API keys.10150 PyPI285Apache 2.0
- FlicenseNot gradedqualityCmaintenanceLocal-first cross-agent memory for AI coding agents. Persistent, shared memory over MCP — what you tell one agent can be recalled by another — with all data stored in a single local SQLite file, no cloud and no API keys.-
- AlicenseNot gradedqualityAmaintenanceZero-GPU, local-first, CPU-native cognitive memory layer for autonomous AI agents with hybrid search (LanceDB + SQLite FTS5), WebUI inspector, and multi-agent shared workspaces.Apache 2.0
- FlicenseNot gradedqualityAmaintenanceProvides AI coding agents with a local-first persistent memory layer they can read and write during sessions, storing decisions, preferences, error patterns, and research per project or globally. Enables semantic and keyword search, formatted context recall, and cross-project guideline surfacing without API keys or cloud storage.-
TDQS
A3.7/5.0
Scored across 18 tools
Disambiguation4/5
Most tools have clearly distinct purposes (search, code search, graph, read, write, checkpoints, etc.). However, rms_search and rms_code_search overlap somewhat since rms_search can already search the code corpus via corpus=code, and rms_sync vs rms_reindex could be confused without reading descriptions carefully.
Naming Consistency4/5
All tools share the rms_ prefix and use snake_case, which is consistent. However, the verb patterns are mixed: some are action-oriented (sync, search, read, write, prune) while others are noun-oriented (checkpoint_done, checkpoint_save, checkpoint_load, checkpoint_query, file_history, wiki_pack, system_instructions). The checkpoint group is consistent internally, but overall the set mixes verb-first and noun-first naming.
Tool Count4/5
18 tools is on the higher end but still reasonable for a memory server that covers sync, search, graph, checkpoints, diagnostics, and project management. Each tool serves a distinct function, though a few could potentially be consolidated (e.g., checkpoint tools are four separate tools but that's a coherent subdomain).
Completeness4/5
The server covers the core memory lifecycle well: write, search, read, sync, reindex, prune, checkpoints, graph queries, and diagnostics. Minor gaps include no explicit tool for deleting/removing notes (rms_prune only archives), and no direct tool for editing existing notes (rms_write saves new content but update semantics are unclear).
Maintenance
ActivityMaintained
ResponsivenessResponsive