AMLink
Related Servers
Alternatives to AMLink
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to query a unified local index of all their sessions through native tools, supporting session summaries, full-text search, listing, message timelines, and handoff context packages for another agent.2MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to collaborate on the same project by sharing session briefs and reading each other's native transcripts, memories, and instructions in place, with zero-copy, across different agent tools.16 npmMIT
- AlicenseAqualityBmaintenanceEnables MCP-capable coding agents to semantically search, store, and inspect a single local, cross-tool index of session histories and project docs. Agents can retrieve what other tools and prior sessions already discovered.3MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to keep sessions short by compacting early, saving a handoff and restoring it afterwards, while automatically recalling relevant project knowledge on every request. It exposes a code map ranked with PageRank and a temporal knowledge graph of decisions, bugs, gotchas and concepts, searched with hybrid BM25, Personalized PageRank and Reciprocal Rank Fusion within a token budget.1 npm13MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to share a persistent, local-first memory of architectural decisions, conventions, bug root causes, and session handoffs, searchable via full-text ranking, so context carries across tools and sessions without any cloud dependency.MIT
- AlicenseNot gradedqualityCmaintenanceProvides persistent cross-session AI memory, code graph analysis, and subagent context compression so coding agents can resume work instantly and avoid re-reading the codebase.Elastic 2.0
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: saving, listing, loading, and refreshing index. No overlap or ambiguity exists, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun snake_case pattern (locate_and_load, list, save_active, refresh). This predictable naming reduces cognitive load and improves discoverability.
With only 4 tools, the server is tightly scoped to session management. Each tool addresses a necessary step in the workflow, and none are redundant or trivial.
The set covers the full lifecycle of session persistence: save, locate, list, and maintain index. There are no obvious gaps that would prevent an agent from completing the core task of transferring sessions between harnesses.