SessionRelay
Related Servers
Alternatives to SessionRelay
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code sessions to automatically capture and retrieve architectural decisions, code changes, bug fixes, and configuration context across sessions using local SQLite storage and hybrid semantic/keyword search.95 PyPI1MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code, Codex and other MCP agents to share one bounded, persistent memory across sessions, so a session starts from what earlier sessions learned instead of re-reading the repository. Storage and retrieval run locally on SQLite full-text search with per-client tokens and scopes, and optional local model enrichment, without any paid model in the path.1MIT
- AlicenseAqualityBmaintenanceLocal memory of your coding-agent sessions. Imports Claude Code, Codex, opencode and Copilot transcripts, extracts decisions and learnings with a link back to the session turn, and lets agents search them over MCP.91MIT
- AlicenseAqualityBmaintenanceShared, local memory for AI coding tools that stays true to your code. Claude Code, Cursor, and Codex share one memory per project; memories are linked to the files they depend on and retired automatically when those files change. Includes a local dashboard, import from CLAUDE.md/AGENTS.md, and export. Runs entirely on your machine.10242 PyPI4MIT

LoreConvoofficial
AlicenseAqualityBmaintenancePersistent memory for AI agents across Claude Code, Cowork, Codex, Cursor and Hermes Agent. Saves, searches and recalls sessions from a local SQLite store through 40+ MCP tools, with auto-save and auto-load hooks, project tagging and export/import. Also a Hermes Agent memory provider plugin in the official catalog. Free: keyword search, 50 sessions. Pro ($8/mo): semantic search and team memory.33169 PyPI12Business Source 1.1- AlicenseNot gradedqualityBmaintenanceGives AI coding agents a private local SQLite memory over MCP so Claude Code, Cursor, and Codex can share approved project lessons, conventions, decisions, and session history without cloud services or telemetry.MIT
TDQS
Scored across 16 tools
Most tools target a clearly distinct action+resource (export/import handoff, save_note, link_sessions, get_decisions, get_stats), and descriptions explicitly state when to use and when not to call each one. The only mild overlap is the discovery trio (search_sessions, suggest_related_sessions, list_sessions) and get_linked_sessions vs suggest_related_sessions, but the keyword-vs-algorithmic-vs-filter distinction is spelled out well enough to disambiguate.
All 16 names follow a consistent snake_case verb_noun pattern (export_handoff, annotate_session, save_note, get_session_detail, list_sessions, set_scope). Verbs are used predictably: get_/list_ for reads, save_/annotate_/link_/set_ for writes, export_/import_ for package transfer.
16 tools is at the upper end of the ideal 3-15 range but each maps to a real capability in the session-memory/handoff lifecycle rather than being redundant. A few could arguably be folded (set_scope as a config tool, get_linked_sessions into get_session_detail), so it is slightly heavy but reasonable.
The surface covers the core lifecycle: capture (save_note, annotate_session), retrieve (search_sessions, get_session_detail, list_sessions, get_decisions, get_file_history, get_unresolved), link/graph, and handoff transfer with quarantine release. Gaps are minor: no delete/forget operation for sessions, notes or decisions, and no explicit add_decision tool (decision capture is only implicit via save_note).