MIHAD
Related Servers
Alternatives to MIHAD
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides coding agents with structured planning, persistent project memory, automated verification, and safety permission controls through MCP tools, enabling better planning, context retention, self-checking, and guarded execution.3 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides AI coding agents with deterministic, attestable org memory via an MCP server, enabling automatic recall of relevant facts on every prompt, loss-proof capture of learnings, and curated promotion of verified facts to a tenant-isolated memory store.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceGives AI coding agents a persistent memory that carries across sessions and projects, letting them save and search decisions, bug fixes, and discoveries through MCP tools. Each new session loads the recent memories of the current project so agents resume with the same context instead of re-explaining it.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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 gradedqualityCmaintenanceProvides AI agents with a governed, three-layer project memory (guide, code facts, and knowledge) through namespaced MCP tools for code search, context compilation, impact analysis, and proposal-driven documentation updates.1 npm2MIT
- FlicenseBqualityBmaintenanceProvides AI coding agents with a hybrid cognitive memory engine that reduces token usage, prevents amnesia, detects repetitive error loops, and retrieves relevant code context through MCP.6-
TDQS
Scored across 4 tools
Each tool targets a distinct action on memory items: recall (read), propose (create), correct (invalidate), and report_outcome (feedback). Their purposes do not overlap, and the descriptions clearly delineate when to use each.
All tools follow a consistent memory_<verb> snake_case pattern: memory_recall, memory_propose, memory_correct, memory_report_outcome. The convention is predictable and readable.
Four tools is well-scoped for a persistent memory interface, covering the essential agent interactions without redundancy. Each tool earns its place in the memory lifecycle.
The set covers read, create, invalidate, and feedback, but lacks explicit update or delete operations. Agents can work around this by proposing new items and marking old ones as wrong, so the gap is minor.