Skip to main content
Glama
Skitchy

Rekindle

by Skitchy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Rekindle

No user-submitted related servers found.

    Related Servers

    • ORA

      black-dash77
      A
      license
      A
      quality
      D
      maintenance
      Persistent memory + intelligent context for Claude Code. Save and reuse solutions, decisions, and patterns across projects.
      43
      7
      MIT

    • am-memory

      danielwanwx
      A
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory for Claude Code — a self-evolving knowledge layer that survives across sessions, grows from every conversation, and surfaces relevant context automatically.
      14
      MIT

    • Colab MCP

      H4RR1SON
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables 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.
      2
      MIT

    • Cozempic

      Ruya-AI
      A
      license
      Not graded
      quality
      C
      maintenance
      2-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.
      173 PyPI
      426
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 10 tools

    Disambiguation4/5

    Memory operations (store/update/delete/list/search) are clearly distinct, and capture operations (capture_now/list_captures/read_capture) form a coherent group. There is some functional overlap between end_session, capture_now, and store_memory since all persist context, but the descriptions draw clear lines between structured handoffs, ad-hoc snapshots, and discrete memories.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (store_memory, delete_memory, list_captures, read_capture, end_session), with memory tools consistently suffixed by _memory/_memories. Deviations like boot_report (noun form) and capture_now (verb_adverb) are minor and still readable.

    Tool Count5/5

    Ten tools is well-scoped for a session-context/memory server, covering memory CRUD, search, session handoff, and capture retrieval without redundancy. Each tool has a defensible role in the workflow.

    Completeness4/5

    Memory lifecycle is fully covered (create, update, delete, list, search) and captures are readable/listable. Minor gaps exist: no get-by-ID for a single memory, no deletion of captures or sessions, and session history is only exposed indirectly via boot_report rather than a list_sessions/read_session pair.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources