memorix and Memory-Plus

memorix
56
Established
Memory-Plus
52
Established
Maintenance 13/25
Adoption 10/25
Maturity 20/25
Community 13/25
Maintenance 2/25
Adoption 13/25
Maturity 24/25
Community 13/25
Stars: 208
Forks: 18
Downloads: β€”
Commits (30d): 0
Language: TypeScript
License: Apache-2.0
Stars: 52
Forks: 7
Downloads: 149
Commits (30d): 0
Language: Python
License: Apache-2.0
No risk flags
Stale 6m

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.

Implements a git-aware memory pipeline that separates commit provenance from reasoning memory, storing both through an MCP server available in stdio mode (per-IDE) or HTTP mode (shared background process). Agents query memory through `memorix_search`, `memorix_timeline`, and `memorix_resolve` tools that apply source-aware retrieval and automatic compaction based on memory formation rules and project binding configuration.

About Memory-Plus

Yuchen20/Memory-Plus

🧠 π‘΄π’†π’Žπ’π’“π’š-𝑷𝒍𝒖𝒔 is a lightweight, local RAG memory store for MCP agents. Easily record, retrieve, update, delete, and visualize persistent "memories" across sessionsβ€”perfect for developers working with multiple AI coders (like Windsurf, Cursor, or Copilot) or anyone who wants their AI to actually remember them.

Built on Google's Embedding API for semantic search, Memory-Plus stores encoded memories locally and supports versioning to track changes over time. It integrates as an MCP server via stdio transport, compatible with VS Code, Cursor, Cline, and other MCP-enabled IDEs, with optional resource-based prompting to control when agents access past context.

Scores updated daily from GitHub, PyPI, and npm data. How scores work