agenthelm
Related Servers
Alternatives to agenthelm
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceOne local memory every coding agent on your machine shares — Claude Code, Cursor, Claude Desktop, OpenCode. Answers from past sessions, commits, CLAUDE.md/AGENTS.md and ADRs with the exact source, and withholds work another agent has claimed so two agents don't rewrite the same thing.34,875 PyPI1MIT
- AlicenseNot gradedqualityDmaintenancePersistent decision memory and contradiction detection for AI coding agents. Enforces architectural consistency across sessions — the agent cannot code until it loads prior decisions. Human resolves conflicts on a dashboard or in chat.1MIT
- AlicenseAqualityBmaintenanceDecision memory for teams building with AI coding agents. Captures every engineering decision once, ranks it by blast radius, and briefs every MCP-compatible agent before it acts, so agents stop making conflicting changes across repos.209 npm11Apache 2.0
- 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
- AlicenseAqualityCmaintenanceLocal-first shared memory and coordination layer for AI coding agents, with repository evidence, reservations, handoffs, code graph context, and dashboard review backed by PostgreSQL/pgvector.303Apache 2.0
- AlicenseCqualityBmaintenanceEnables Claude Code agents and sub-agents to share a persistent, compiled memory of project state, decisions, tasks, and facts across sessions instead of re-reading transcripts. Provides token-efficient bootstrap, search, commit, leased task claiming, and task-specific context compilation so parallel agents can coordinate without clobbering each other.510 npmMIT
TDQS
Scored across 3 tools
Each tool targets a distinct operation on the Project Brain: retrieval of context, submission of new knowledge, and querying history. There is no overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (get_context, propose_knowledge, get_history). The repetition of 'get' is acceptable as it indicates retrieval operations.
With only 3 tools, the server is scoped for a focused knowledge management function. While minimal, each tool serves a clear purpose and the count is appropriate for the domain.
The tools cover retrieval, submission, and history, but lack direct update or delete operations for knowledge items. Updates could be handled via new proposals, but that introduces overhead and gaps.