CONTINUITY
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@CONTINUITYsave session with handoff for my-project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
CONTINUITY
Session State Persistence for AI Systems
Crashes lose seconds, not hours. Every AI instance picks up exactly where the last one left off.
The Problem
AI assistants are stateless by design. Every session starts fresh. This is fine for one-off questions but catastrophic for multi-session projects where architectural decisions compound and context is everything.
Sessions crash, hit token limits, or end — and the next one starts blind
Architectural decisions get re-debated from scratch
Completed work gets forgotten; hours vanish into reconstruction
The same problems get solved repeatedly across different codebases
Related MCP server: JauMemory MCP Server
The Solution
8 tools that handle session persistence, crash recovery, decision tracking, and context compression. Plug CONTINUITY into Claude Desktop (or any MCP-compatible client) and session continuity becomes automatic.
It's the difference between a collaborator who remembers your project and one who asks "so what are we working on?" every morning.
Tools
Tool | Purpose |
| Generate structured handoff at session end |
| Resume from last session with compressed context |
| Lightweight state save every 3-5 operations |
| Detect crash and auto-recover from last checkpoint |
| Record architectural decisions with rationale + alternatives |
| Search decision history to prevent re-debates |
| Smart context compression (20K tokens → 1K) |
| Validate handoff completeness before saving |
Installation
Prerequisites
Node.js >= 18
Claude Desktop or any MCP-compatible client
Setup
git clone https://github.com/duke-of-beans/CONTINUITY.git
cd CONTINUITY
npm install --include=dev
npm run buildConfigure Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"CONTINUITY": {
"command": "node",
"args": ["/path/to/CONTINUITY/dist/index.js"],
"env": {
"CONTINUITY_DATA_DIR": "/path/to/your/.continuity"
}
}
}
}Restart Claude Desktop. You'll see 8 new tools available.
Configuration
CONTINUITY_DATA_DIR controls where state is stored. Defaults to ~/.continuity.
.continuity/
├── config.json # Settings (auto-generated with defaults)
├── state.db # SQLite database
├── sessions/ # JSON state snapshots + markdown handoffs
└── decisions/ # JSONL decision logUsage
Session Lifecycle
Session Start:
→ continuity_recover_crash() # Check for unclean shutdown
→ continuity_load_session() # Load last session context
During Work:
→ continuity_checkpoint() # Every 3-5 tool calls
→ continuity_log_decision() # When architectural choices are made
Session End:
→ continuity_handoff_quality() # Validate completeness
→ continuity_save_session() # Generate handoff for next sessionDecision Registry
Stop re-debating the same architectural choices:
continuity_log_decision({
workspace: "my-project",
category: "architectural",
decision: "Use PostgreSQL over Neo4j",
rationale: "Simpler ops, graph extension covers graph needs",
alternatives: ["Neo4j", "DGraph", "ArangoDB"],
impact: "high",
revisit_trigger: "If graph queries exceed 10K nodes/sec"
})Later, in any new session:
continuity_query_decisions({ keyword: "database", workspace: "my-project" })
// → Returns the decision with full rationale, preventing re-debateCrash Recovery
continuity_recover_crash({ workspace: "my-project" })
// → Detects unclean shutdown
// → Returns last checkpoint with active files, next steps, recovery context
// → Zero context loss if checkpoints were regularArchitecture
Storage Layer
├── SQLite (state.db) → Checkpoints, session records, fast queries
├── JSONL (decisions.jsonl) → Append-only architectural decision log
└── JSON (sessions/*.json) → Full session state snapshots + markdown handoffs
Tool Modules
├── session-tools.ts → save, load, checkpoint, crash recovery
├── decision-tools.ts → log + query architectural decisions
└── utility-tools.ts → compression, handoff validation
Server
└── mcp-server.ts → MCP SDK wiring, tool registration, error handlingWorks With
Compatible with Claude Desktop, Cursor, and any MCP-compatible client. Designed to compose with other MCP servers — any server can trigger checkpoints via the standard tool interface.
License
MIT — Use it, fork it, build on it.
Author
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/duke-of-beans/CONTINUITY'
If you have feedback or need assistance with the MCP directory API, please join our Discord server