A
licenseNot graded
qualityC
maintenanceProvides a memory layer for AI coding agents with Git-powered version control, enabling automatic tracking of prompts, context, and code diffs.
192
MIT
Perenna
by scarletkc
Related Servers
Alternatives to Perenna
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenancePersistent, structured memory for AI coding agents via a git-like filesystem with branch/commit/merge tools, enabling agents to maintain context across sessions.MIT
- AlicenseAqualityAmaintenanceGit-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
robo-cortexofficial
AlicenseAqualityAmaintenanceProvides a git-aware knowledge base for AI coding agents to store and retrieve memories anchored to code changes, with automatic staleness detection.81MIT- AlicenseNot gradedqualityAmaintenanceOpen-source persistent memory infrastructure for AI agents.150323Apache 2.0
- FlicenseNot gradedqualityAmaintenancePersistent memory for AI coding agents: local-first semantic search, dependency graphs, git history.1-
TDQS
A4.2/5.0
Scored across 3 tools
Disambiguation5/5
Each tool handles a distinct lifecycle operation: reading/querying, writing/updating, and deleting memories. There is no overlap between the primary actions, and the sub-modes within memory_read are explicitly separated (list, search, get).
Naming Consistency5/5
All tool names follow the same memory_verb pattern using clear, lowercase snake_case verbs. The naming makes the operation type immediately obvious and perfectly consistent across the set.
Tool Count5/5
Three tools is a compact but complete surface for a permanent memory store. Each tool earns its place, and no redundant or extraneous operations exist.
Completeness5/5
The set covers the full lifecycle: create/modify via memory_write, read via memory_read (including list/search/get), and delete via memory_delete. Revision-handling and Git-history recovery details further round out the functionality, leaving no critical gaps.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive