MCP Continuation Notes
Manages continuation notes for projects, enabling session handoff and historical browsing through a two-location storage system.
README
MCP Continuation Notes
MCP server for managing continuation notes with automatic session handoff capabilities.
🎯 Purpose
This MCP server implements the Continuation Note Protocol as code, providing:
- Project-specific continuation notes stored in project directories
- Session handoff mechanism through a standard location
- Built-in protocol enforcement ensuring consistent note structure
- Historical browsing of project continuation notes
🏗️ Architecture
Two-Location System
- Project Storage:
{project}/continuation-notes/continuation-{timestamp}.md - Handoff Location:
/Users/bard/Code/claude-brain/data/continuation-note-latest.md
Workflow
- Write: Save to project + copy to handoff location
- Read: Startup reads from handoff location
- Cleanup: Delete from handoff (original stays in project)
- Browse: View project history anytime
🛠️ Tools
continuation_write
Creates a continuation note following the built-in protocol structure.
Required Parameters:
project: Project nameproject_path: Full path to project directoryphase: Current project phasestatus: Current statuscontext_bridge: Context for next session
Optional Parameters:
completion_percentage: 0-100major_achievements: Array of achievementsnext_actions: Array of next actionscritical_factors: Array of success factorstesting_criteria: Array of validation criteriaadditional_content: Extra content
continuation_read_and_cleanup
Reads the handoff note and deletes it (for startup processing).
continuation_check_handoff
Checks if a handoff note exists without reading it.
continuation_list_for_project
Lists all continuation notes for a specific project.
continuation_read_project_note
Reads a specific continuation note from project directory.
🎨 Protocol Implementation
The server automatically generates notes with this structure:
# 📋 Continuation Note - {project} - {date}
## 🎯 Session Status Dashboard
**Project**: {project}
**Phase**: {phase}
**Status**: {status}
**Completion**: {percentage}%
### ✅ Major Achievements This Session
- Achievement 1
- Achievement 2
## 📚 Context Bridge for Next Session
{context_bridge}
## 🚀 Next Actions
- Action 1
- Action 2
### Critical Success Factors
- Factor 1
- Factor 2
## 🎯 Session Continuity
Expected behavior on restart...
🔧 Installation
Add to your MCP client configuration:
{
"mcpServers": {
"mcp-continuation-notes": {
"command": "node",
"args": ["/Users/bard/Code/mcp-continuation-notes/src/index.js"],
"disabled": false
}
}
}
📋 Usage Example
// Write a continuation note
continuation_write({
project: "brain-system-protocol-execution-integration",
project_path: "/Users/bard/Code/claude-brain",
phase: "Phase 9 - Testing Enhanced Startup",
status: "Ready for validation",
completion_percentage: 85,
major_achievements: [
"Built MCP continuation notes server",
"Implemented protocol as code",
"Created two-location architecture"
],
context_bridge: "MCP server built and ready for testing. Next session should validate the handoff mechanism.",
next_actions: [
"Test continuation_read_and_cleanup",
"Validate project storage",
"Add to Claude Desktop config"
],
critical_factors: [
"Handoff note should be automatically processed",
"Project notes should remain for browsing",
"Protocol structure should be enforced"
]
})
// Check for handoff note (at startup)
continuation_check_handoff()
// Read and process handoff note (at startup)
continuation_read_and_cleanup()
// Browse project history
continuation_list_for_project({
project_path: "/Users/bard/Code/claude-brain"
})
🎉 Benefits
- ✅ Protocol as Code: No separate protocol document to maintain
- ✅ Consistent Structure: Every note follows the same format
- ✅ Project History: All notes archived per-project
- ✅ Clean Handoffs: Single location for session transitions
- ✅ Self-Documenting: Tool parameters define the protocol
🔄 Integration
This server is designed to integrate with:
- Brain System: Enhanced startup protocol
- Project Management: Brain Manager project context
- Session Continuity: Seamless session transitions
Status: Ready for testing and integration
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.