memorix
Related Servers
Alternatives to memorix
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceCross-tool AI memory engine providing 25 MCP tools for semantic memory, session guard, trace auditing, and proactive IDE interception, all locally without API keys.3 npm3AGPL 3.0
- AlicenseAqualityAmaintenanceSelf-hosted memory and governance layer for AI coding agents. 28 MCP tools with hybrid search, structured knowledge capture, behavioral nudges, and git-native storage. Zero cloud dependencies.306Business Source 1.1
- 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 gradedqualityAmaintenanceEnables teams of AI coding agents (Claude Code, Cursor, Codex) to share persistent, time-aware graph memory and coordinate their work via MCP, so agents recall verified fixes at the moment of failure, learn procedures automatically, avoid file conflicts, claim tasks race-free, and hand off facts and decisions between sessions.MIT
- AlicenseNot gradedqualityDmaintenanceObsidian-backed knowledge graph with semantic search, entity extraction, and cross-session memory. 11 MCP tools. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible editor.96 npm1MIT
- AlicenseBqualityAmaintenanceLets multiple AI agents and parallel coding sessions share one memory and task ledger, so they can claim work instead of duplicating it, resume each other's handoffs and reasoning, and use credentials without ever seeing the keys. Connects assistants such as Claude Code, Codex, Cursor, Gemini, ChatGPT and custom agents over MCP, backed by a single local SQLite file or a self-hosted Postgres hub.35MIT
TDQS
Scored across 9 tools
Most tools are clearly distinct: search, store, detail, resolve, session start, project context, codegraph status, and media. However, 'memorix_project_context' and 'memorix_session_start' both provide context/handoff information, with some overlap in purpose (one is a brief, the other a continuation card), which could cause minor confusion.
All tools use the 'memorix_' prefix with descriptive nouns (search, store, detail, resolve, etc.). The only minor deviation is 'memorix_media' (a noun rather than a verb-based action) but it is still clear. Overall, naming is consistent and predictable.
With 9 tools, the number is well-scoped for a memory management server. Each tool covers a specific aspect (store, search, retrieve, resolve, session management, context building, status check, media handling), and none feel redundant or excessive. This is within the ideal range.
The tool surface covers core memory operations: store, search, retrieve, resolve, and session tracking. Missing would be an update/edit tool for memories (only resolve exists for modification), but the descriptions indicate memories are immutable observations, so this may be intentional. However, a delete tool isn't present (only CLI for destructive removal), but this is acceptable.