Skip to main content
Glama
MikeyBeez

MCP Continuation Notes

by MikeyBeez
README.md
# 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
1. **Project Storage**: `{project}/continuation-notes/continuation-{timestamp}.md`
2. **Handoff Location**: `/Users/bard/Code/claude-brain/data/continuation-note-latest.md`

### Workflow
1. **Write**: Save to project + copy to handoff location
2. **Read**: Startup reads from handoff location 
3. **Cleanup**: Delete from handoff (original stays in project)
4. **Browse**: View project history anytime

## πŸ› οΈ Tools

### `continuation_write`
Creates a continuation note following the built-in protocol structure.

**Required Parameters**:
- `project`: Project name
- `project_path`: Full path to project directory
- `phase`: Current project phase
- `status`: Current status
- `context_bridge`: Context for next session

**Optional Parameters**:
- `completion_percentage`: 0-100
- `major_achievements`: Array of achievements
- `next_actions`: Array of next actions
- `critical_factors`: Array of success factors
- `testing_criteria`: Array of validation criteria
- `additional_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:

```markdown
# πŸ“‹ 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:

```json
{
  "mcpServers": {
    "mcp-continuation-notes": {
      "command": "node",
      "args": ["/Users/bard/Code/mcp-continuation-notes/src/index.js"],
      "disabled": false
    }
  }
}
```

## πŸ“‹ Usage Example

```javascript
// 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

TDQS

A4/5.0

Scored across 7 tools

Disambiguation4/5

Tools are mostly distinct: write, read (three variants), delete, check, list. The three read tools overlap slightly, but their intended use cases are clearly described (read-and-cleanup, read-with-staleness, read-without-staleness) and one is deprecated, reducing ambiguity.

Naming Consistency5/5

All tool names follow a consistent pattern: continuation_ prefix plus a verb phrase (write, read_and_cleanup, read_with_staleness, cleanup_old, check_handoff, list_for_project, read_project_note). The naming is perfectly uniform and predictable.

Tool Count5/5

With 7 tools, the server is well-scoped for the single purpose of managing continuation notes. Each tool serves a clear lifecycle function (write, read, check, list, delete) without bloat or redundancy.

Completeness5/5

The tool set covers the full continuation‑note lifecycle: creation (write), retrieval (read variants), existence checking, listing for a project, and deletion. No obvious gaps exist; the write tool replaces previous notes, so an explicit update is unnecessary.

Maintenance

ActivityMaintained
ResponsivenessNo issues