Rekindle
Keep long-running agent coding sessions coherent across restarts with SQLite-backed continuity instead of brittle chat exports.
Overview
Rekindle is an MCP server for the Build phase that restores agent session continuity via boot reports, orientation scoring, and end-session capture backed by SQLite.
What is this MCP server?
- Boot reports summarize prior session state when MCP starts
- Orientation scoring measures how aligned the agent is with ongoing work
- End-session capture writes structured closure before you close the IDE
- Local SQLite storage for continuity metadata (npm stdio package rekindle v0.2.1)
- stdio MCP transport fits Claude Code, Cursor, and other local agent hosts
- Server version 0.2.1
- Transport: stdio via npm identifier rekindle
- Persistence: SQLite (per server description)
Community signal: 3 GitHub stars.
What problem does it solve?
Every new agent session forces you to reconstruct decisions, open tasks, and repo context from memory or scattered notes.
Who is it for?
Indie developers running multi-day Claude Code or Cursor sessions on one codebase who want local, MCP-native continuity.
Skip if: Teams that only need shared human documentation in Notion or Linear and rarely restart agent sessions.
What do I get? / Deliverables
After you connect Rekindle, agents start with structured boot context and you can close sessions with captured state ready for the next run.
- Boot report on MCP startup summarizing prior session orientation
- End-session capture artifact stored locally
- Orientation score you can use before delegating more agent work
Recommended MCP Servers
Journey fit
Rekindle is installed where builders wire MCP into their agent stack, but its value shows up whenever coding sessions stop and restart. Session boot reports, orientation scoring, and end-of-session capture are agent-workflow primitives, not app feature code.
How it compares
MCP session-memory layer, not a project-management skill or hosted chat memory SaaS.
Common Questions / FAQ
Who is Rekindle for?
Solo builders and small teams using MCP-enabled coding agents who restart sessions often and want SQLite-backed continuity on their machine.
When should I use Rekindle?
Use it when you configure agent tooling and whenever you finish a coding block so the next session inherits orientation and closure metadata.
How do I add Rekindle to my agent?
Install the npm package rekindle (stdio), register io.github.Skitchy/rekindle in your MCP config, and restart the agent host so boot tools load.