LogNexus
OfficialRelated Servers
Alternatives to LogNexus
AlicenseNot gradedqualityFmaintenanceLiving memory for AI coding agents (Claude Code, Cursor, Copilot, Codex). Cross-vendor persistent memory, decision recall, and outcome calibration via MCP and hooks.301 npmApache 2.0
Related Servers
- AlicenseBqualityAmaintenancePersistent, local memory for AI coding agents that learns how you work, not just what you said. Supports Claude Code, Codex CLI, Cursor, and any MCP client.79235 PyPI73MIT
- AlicenseNot gradedqualityBmaintenancePersistent project memory and task management for AI coding agents through MCP. Lets Claude Code, Cursor, Codex and other MCP clients save decisions and bug fixes, search relevant context, and reuse it across sessions.1MIT
- AlicenseNot gradedqualityAmaintenanceGives AI coding agents persistent, cross-session memory by storing task insights as interlinked markdown knowledge cards and recalling relevant ones before new work begins. Uses plain files and git sync instead of a vector database or embeddings, and exposes this through MCP tools for Claude Code, Cursor, VS Code Copilot, Codex, Windsurf, and other clients.10 npmISC
- AlicenseAqualityCmaintenancePersistent memory MCP server for Claude Code, Cursor, and GitHub Copilot. Semantic search, Git sync, project-based, Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot. Semantic search, Git sync, project-based organization, and team collaboration via Model Context Protocol.11415 npm2MIT
- AlicenseAqualityBmaintenanceShared, versioned memory for your agents across Claude Code, Cursor, Kiro and Grok. One MCP server, sourced answers, full history.3MIT
- AlicenseAqualityAmaintenanceMCP server that gives coding agents persistent, verified memory of codebase decisions, conventions, and skills, with evidence-based claims that are re-checked via git hooks and human-gated review. Enables memory search, propose/approve, chat harvesting, and critique across MCP-compatible tools.2163 npm1MIT
TDQS
Scored across 12 tools
The tools mostly have distinct purposes, and descriptions explicitly cross-reference alternatives. However, a couple of boundaries still require careful reading, especially lognexus_state_finish_task versus lognexus_commit with finishTask:true, and lognexus_status versus lognexus_state_get.
All tools share the lognexus_ prefix and use snake_case, with clear state_* and note_* action subgroups. Minor deviations are the top-level bare nouns/verbs such as lognexus_status, lognexus_audit, and lognexus_telemetry.
Twelve tools fit the workflow-management scope well. Each tool covers a meaningful state, commit, review, note, timeline, or telemetry operation without obvious filler.
The surface covers the core lifecycle: state inspection/sync, task set/finish/clear, commit creation, Git Notes, audit, timeline, and telemetry. Minor gaps exist around higher-level GitHub operations such as opening or merging a PR directly, though timeline and audit support the surrounding workflow.