memorix and memory-journal-mcp
These two tools are ecosystem siblings: Project A leverages MCP (Memory Control Protocol) as its underlying mechanism for cross-IDE memory persistence, while Project B specifically provides an MCP server designed for managing AI context and project intelligence.
About memorix
AVIDS2/memorix
Cross-Agent Memory Bridge Persistent memory for AI coding agents across 10 IDEs (Cursor, Windsurf, Claude Code, Codex, Copilot, Kiro, Antigravity, OpenCode, Trae, Gemini CLI) via MCP. Team collaboration, auto-cleanup, mini-skills, workspace sync. Never re-explain your project again.
This project gives AI coding agents a shared, persistent memory that goes beyond a single conversation or IDE. It helps developers and engineering teams using multiple AI coding agents like GitHub Copilot or Gemini CLI by allowing agents to remember past project details, decisions, and reasoning across different sessions and development environments. The result is that you don't have to re-explain your project to your AI assistant repeatedly.
About memory-journal-mcp
neverinfamous/memory-journal-mcp
MCP Server for AI Context + Project Intelligence. Overcome Disconnected AI Sessions with Persistent Project Memory, Automatic Session Briefing & Summation, Triple Search, Knowledge Graphs, GitHub Integration (Actions, Insights, Issues, Kanban, Milestones, and PRs), Automated Scheduling, 42 Tools, Tool Filtering, and HTTP/SSE & stdio Transport.
This tool helps project managers and team leads using AI assistants overcome the problem of AI 'forgetting' past project context. It ingests your project's activity and AI conversations, then provides a persistent, searchable memory and automatically briefs AI agents on relevant history for ongoing tasks. This is ideal for development teams and managers who rely on AI for support in complex, long-running software projects.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work