Rekindle
Related Servers
Alternatives to Rekindle
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenancePersistent memory + intelligent context for Claude Code. Save and reuse solutions, decisions, and patterns across projects.437MIT
- AlicenseNot gradedqualityDmaintenanceProvides persistent memory for Claude Code, automatically extracting and surfacing relevant context from past sessions to avoid re-explaining issues and decisions.MIT
- AlicenseAqualityAmaintenanceZero-config session continuity for Claude Code. Automatically captures and restores project context across sessions using Claude Hooks.25340 npm6MIT
- AlicenseNot gradedqualityDmaintenancePersistent memory for Claude Code — a self-evolving knowledge layer that survives across sessions, grows from every conversation, and surfaces relevant context automatically.14MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI coding assistants like Claude Code, Cursor, and Codex to share chat logs, terminal history, and session context with each other. Eliminates the need to re-explain context when switching between different AI coding tools.2MIT
- AlicenseNot gradedqualityAmaintenance2-5x longer Claude Code sessions before compaction. Saves 30-40% on input token costs. Remembers your rules and corrections so Claude stops repeating mistakes after compaction. Auto-runs in the background, just install once and forget about it.379MIT
TDQS
Scored across 10 tools
Most tools have distinct purposes: memory CRUD vs. session handoff vs. capture recovery. The only potential confusion is between capture_now and end_session, but descriptions clarify that end_session creates a structured handoff while capture_now preserves raw context for compaction recovery.
All tool names follow a consistent snake_case verb-first pattern: end_session, list_captures, read_capture, store_memory, search_memory, list_memories, delete_memory, update_memory. Even boot_report and capture_now fit the verb-first style. No mixed conventions or unpredictable naming.
Ten tools is well within the ideal 3-15 range and each tool serves a clear function in the memory/session management domain. No redundancy or bloat; the set feels appropriately scoped for the server's purpose.
Memory CRUD is covered (store, search, list, update, delete) and session handoff/orientation is addressed with end_session and boot_report. However, there's no direct 'get memory by ID' tool, which could force agents to use search or list and manually filter, a minor gap in the read path.