Memory Journal MCP Server
Related Servers
Alternatives to Memory Journal MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceProvides AI coding assistants with persistent project memory by capturing development checkpoints during git commits, branch switches, and inactivity. It enables seamless task resumption through tools that retrieve session history, momentum, and synthesized re-entry briefings.3MIT
- AlicenseNot gradedqualityDmaintenanceNever start from zero. Persistent session intelligence for AI coding assistants.70 npm1MIT
- AlicenseCqualityBmaintenanceTurns AI assistants into active Technical Project Managers by providing a persistent project brain and workflow tools for onboarding, session management, and code verification.9143 PyPI2MIT
- AlicenseBqualityBmaintenancePersistent memory and session intelligence for AI coding assistants. Auto-tracks mistakes, decisions, and context via hooks. Mines your full session history for patterns, predictions, and cross-session search.2116MIT
- AlicenseNot gradedqualityCmaintenanceAutomatically captures project state on git commits, detects context drift, and delivers structured token-budgeted briefings to AI agents, ensuring project continuity without manual effort.85 npm2MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI coding assistants with persistent, context-rich memory of a codebase, including documentation and git history, enabling recall across sessions.105Apache 2.0
TDQS
Scored across 113 tools
The set has many overlapping tools: search_entries overlaps with semantic_search and search_by_date_range, personal and team variants mirror each other, and read_resource/mj_read_resource/memory_read_resource are essentially fallback aliases. Team-prefixed tools are distinguishable, but an agent faces real misselection risk across search, backup, import/export, vector-index, and GitHub issue/PR/kanban operations.
Most tools use snake_case and the team_* subset is consistently prefixed, which helps. However, personal tools are unprefixed, GitHub tools use mixed patterns (get_github_issues vs move_kanban_item vs close_github_issue_with_entry), and a few names use kebab-case or test/fallback conventions, making the overall naming only moderately predictable.
With 113 tools, the surface is far beyond a reasonable scope even for a feature-rich memory journal server. The extensive mirroring between personal and team databases, plus test/fallback handlers and auxiliary GitHub/git tools, makes the set heavy and hard to navigate.
The memory-journal domain is covered very thoroughly: CRUD, batch operations, search modes, tagging, relationships, imports/exports, backups, restore, vector indexing, statistics, and team collaboration all exist. Minor gaps remain, such as no obvious team restore-backup counterpart and limited GitHub issue lifecycle operations beyond close-with-entry.