Context Continuation MCP Server
Works with git version control through file-based storage of context tracking data in human-readable markdown files, facilitating project history management across development sessions.
Stores session data and project information in human-readable markdown files, enabling easy review and version control of context data.
Click on "Deploy 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., "@Context Continuation MCP Server start tracking this session and let me know when we're near the token limit"
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.
Context Continuation MCP Server
An MCP (Model Context Protocol) server that provides intelligent context management for AI development sessions. Never lose context when hitting token limits again!
Features
Automatic Context Tracking: Monitor token usage and conversation flow
Intelligent Session Breaks: Get notified before hitting context limits
Seamless Restoration: Generate context restoration prompts for new sessions
Project Management: Track milestones, decisions, and progress across sessions
File-Based Storage: Human-readable markdown files that work with git
Related MCP server: Context Management System
Quick Start
Installation
npm install -g context-continue-mcpUsage with Claude Desktop
Add to your Claude Desktop configuration:
{
"mcpServers": {
"context-continue": {
"command": "context-mcp",
"args": ["--project", "/path/to/your/project"]
}
}
}Restart Claude Desktop
Start using context tools in your conversations:
context_start_session- Begin tracking a new sessioncontext_track_message- Track important messagescontext_get_status- Check token usagecontext_restore_session- Generate restoration prompt
Tools Available
Session Management
context_start_session- Start tracking a new context sessioncontext_end_session- End current session with summarycontext_get_status- Get current session and token usage info
Context Tracking
context_track_message- Add message to session trackingcontext_track_progress- Update project progresscontext_add_milestone- Add project milestone
Restoration
context_restore_session- Generate context restoration promptcontext_get_project_summary- Get full project overview
How It Works
Start a Session: Initialize context tracking for your project
Track Progress: Important messages and decisions are automatically logged
Monitor Usage: Get warnings when approaching token limits
Seamless Continuation: Generate restoration prompts for new sessions
File Structure
The server creates a .context directory in your project:
your-project/
├── .context/
│ ├── config.json
│ ├── project_summary.md
│ ├── sessions/
│ │ ├── session_001_2025-05-31.md
│ │ └── session_002_2025-06-01.md
│ ├── progress/
│ │ ├── milestones.md
│ │ └── decisions.md
│ └── artifacts/
└── your-code/Quality Assurance
This project maintains high code quality through:
🧪 Comprehensive Testing: 43+ unit tests with 95%+ coverage
🔄 Continuous Integration: Automated testing on Node.js 18.x, 20.x, 21.x
🌍 Cross-Platform: Tested on Ubuntu, Windows, and macOS
📊 Code Coverage: Real-time coverage tracking with Codecov
🏗️ Build Verification: Automated build and CLI functionality testing
📦 Package Validation: Pre-publish testing and compatibility checks
Running Tests
# Run all tests
npm test
# Run tests with coverage
npm run test:coverage
# Run specific test suites
npm test token-counter
npm test session-tracker
npm test context-manager
# Watch mode for development
npm run test:watchDevelopment
git clone https://github.com/core3-coder/context-continue-mcp
cd context-continue-mcp
npm install
npm run build
npm startLicense
MIT - see LICENSE file for details
Available Tools
8 toolscontext_add_milestoneC
Add a project milestone
Inputs: projectPath (required), title (required), description, status.
context_end_sessionC
End the current context tracking session
Inputs: summary.
context_get_project_summaryC
Get a comprehensive project summary
Inputs: projectPath (required).
context_get_statusB
Get current session status and token usage
Inputs: no named parameters.
context_log_decisionC
Log a technical decision
Inputs: decision (required), projectPath (required), title (required), alternatives, +3 more.
context_restore_sessionC
Generate a context restoration prompt for continuing work
Inputs: projectPath (required).
context_start_sessionC
Start a new context tracking session
Inputs: projectPath (required), sessionName.
context_track_messageC
Track a message in the current session
Inputs: message (required), role (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no overlap: session management (start, end, restore), status tracking (get_status, track_message), project operations (add_milestone, get_project_summary), and decision logging. The descriptions reinforce unique functions, making tool selection unambiguous.
All tools follow a consistent 'context_verb_noun' pattern with snake_case throughout (e.g., context_start_session, context_log_decision). This predictable naming scheme enhances readability and makes the tool set cohesive and easy to navigate.
With 8 tools, the count is well-scoped for a context tracking server, covering session lifecycle, status monitoring, project management, and decision logging. Each tool earns its place without redundancy, fitting a typical range for this domain.
The tool set provides complete coverage for context tracking: session lifecycle (start, end, restore), real-time updates (track_message, get_status), project management (add_milestone, get_project_summary), and decision documentation (log_decision). No obvious gaps exist, enabling agents to handle all core workflows seamlessly.
Maintenance
Related MCP Connectors
Bring your saved preferences, project decisions, and useful context into your next AI conversation.
Intelligent context infrastructure for AI teams: knowledge graph, sessions, tasks, documents.
Persistent context for Claude. Your AI always knows your projects and next actions across sessions.
Cross-LLM persistent memory: store context once, recall it from any AI model.
Related MCP Servers
- FlicenseBqualityFmaintenanceProvides sophisticated context management for Claude, enabling persistent context across sessions, project-specific organization, and conversation continuity.415-
- FlicenseNot gradedqualityDmaintenanceEnables AI development tools to maintain context across chat sessions with automatic branching, progress tracking, and TODO management for different tasks.-
- AlicenseNot gradedqualityCmaintenanceProvides persistent context management for Claude AI coding assistants, allowing you to save and restore conversation context, create checkpoints, and organize information across sessions to prevent losing important work history and decisions during long coding sessions.195 npm136MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to persist and restore context across sessions, preserving decisions, progress, files, and checkpoints. It supports topic-based channels, search, change tracking, git-aware correlation, batch operations, and shared memory across parallel sessions.195 npmMIT