Context Manager MCP Server
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
Integrations
Used for package management and running scripts for development, building, and production deployment of the MCP server
Client session tracking, capability negotiation, and state persistence between interactions
Socket-based transport implementation for reliable network communication with connection and event management
Context Manager MCP Server
A Model Context Protocol (MCP) server implementation for managing development context and workflow.
Features
- Socket-based transport with reliable message framing
- Full JSON-RPC 2.0 protocol support
- Session management with capability negotiation
- Extensible tool registry system
- Project, workpackage, and task management
- Checkpoint and restore functionality
- QA review workflow support
Initial Setup
Usage
Starting the Server
Development Mode
Clean Start
If you encounter any issues, you can try a clean build:
Architecture
Core Components
- Message Framing
- Content-Length based protocol
- Reliable message boundary handling
- Buffer management
- Transport Layer
- TCP socket-based communication
- Connection management
- Event-driven architecture
- Session Management
- Client session tracking
- Capability negotiation
- State persistence
- Tool Registry
- Dynamic tool registration
- Input validation
- Result formatting
Tools
- Project Management
- Create/Get projects
- Project checkpoints
- State restoration
- Work Package Management
- Create/Get work packages
- Progress tracking
- Status updates
- Task Management
- Create/Update tasks
- File change tracking
- Task checkpointing
- QA Tools
- Review workflow
- Fix requests
- Work package acceptance
Configuration
Environment variables:
DEBUG
: Enable debug logging (0/1)MCP_PORT
: Server port (default: 44557)
Protocol
The server implements the Model Context Protocol with JSON-RPC 2.0:
Message Flow
- Client connects via TCP
- Client sends initialize request
- Server responds with capabilities
- Normal message exchange begins
- Client can shutdown/exit
Development
See Initial Setup and Development Mode sections above.
Contributing
- Fork the repository
- Create your feature branch
- Commit your changes
- Push to the branch
- Create a Pull Request
License
ISC License
This server cannot be installed
A server implementation of the Model Context Protocol (MCP) for managing development workflow with features like project management, task tracking, and QA review support.