aci-mcp
Related Servers
Alternatives to aci-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides persistent local memory for any MCP-compatible AI agent, enabling agents to store, search, recall, forget, export, and manage preferences, rules, and facts with zero dependencies, no cloud, and no API keys.8MIT
- AlicenseNot gradedqualityBmaintenanceProvides local-first persistent memory with a typed knowledge graph and bounded multi-hop retrieval via MCP, letting coding agents and local LLM systems store, search, and recall facts across sessions without hosted services or model dependencies.MIT
- AlicenseCqualityAmaintenanceProvides AI agents with a human-inspired memory layer via MCP, enabling episodic and semantic memory recall, forgetting curves, consolidation, and contradiction detection. It integrates with MCP clients to offer local-first, dependency-free memory management.981MIT
- AlicenseNot gradedqualityDmaintenanceLocal-first AI memory layer with hybrid retrieval and brain-inspired namespaces. Enables agents to save, search, and manage memories directly via MCP tools.3 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides a local-first, source-cited memory layer for AI agents, with MCP tools to search, read, explain sources, and propose/apply memory updates.26 npm7Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI harnesses to maintain a persistent memory layer backed by a local SQLite file, providing MCP tools to add, search, deprecate, and synchronize facts without deleting history.MIT
TDQS
Scored across 9 tools
Tools orgainize into three recognizable domains — personal memory (recall/remember/ingest/validate), shared skills (find/save/outcome), and collaboration (post/team_activity) — with clear read/write pairs. Two pairs (recall vs validate and remember vs ingest) could cause initial misselection, but their descriptions give distinct triggers: search-by-meaning vs claim-checking, and single-fact vs folder ingestion.
All tools share the aci_ prefix in snake_case, with most following a verb (recall, remember, ingest, validate) or verb+object pattern (find_skills, save_skill, post_work). aci_skill_outcome and aci_team_activity break the verb convention with noun-noun names, a minor deviation in an otherwise predictable scheme.
Nine tools cover three cohesive subdomains — memory (4), skills (3), and shared work log (2) — with each tool serving a distinct purpose and no apparent redundancy. This sits comfortably in the well-scoped 3-15 range for a server of this breadth.
Memory has write (remember/ingest), read (recall), and verification (validate) but no explicit forget/delete tool; agents can work around this via re-storing corrections. Skills have a full find/save/feedback lifecycle, and the work log has both write and read sides, so core workflows are well covered with only a minor gap.