mcp s

Collection of Model Context Protocol (MCP) servers for enhanced session management and task automation

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio kayi2215-mcp-servers node servers/task-manager/index.js \
  --env DB_PATH="./data/sessions.db" \
  --env LOG_LEVEL="info"

How to use

This MCP server bundle provides two interconnected servers: an Enhanced Session Manager and a Task Management Server. The Enhanced Session Manager handles advanced session workflows, including checkpoints, indexing, change tracking, and search across sessions. The Task Management Server focuses on project and task tracking, component management, and progress monitoring. To start using them, initialize the Node.js environment and run each server's entry point as shown in the usage examples. The two servers can share a common data store via the configured environment variables. Users can leverage the session manager to restore or branch sessions using checkpoints, while the task manager enables organizing work items and tracking progress across components and projects.

How to install

Prerequisites:

Node.js (LTS version) and npm installed on your system.
Git (optional, for cloning the repository).

Clone the repository or download the package.
Navigate to the project directory: cd path/to/mcp-servers
Install dependencies: npm install
Configure environment (optional): Create a .env file or rely on the defaults in the mcp_config (DB_PATH and LOG_LEVEL).
Start the servers (see usage):
- Start Enhanced Session Manager: node servers/session-manager/index.js
- Start Task Management Server: node servers/task-manager/index.js

Additional notes

Environment variables:

DB_PATH controls where session data is stored (e.g., SQLite database). Ensure the directory exists or create it before running.
LOG_LEVEL can be set to debug, info, warn, or error to control verbosity. Common issues:
If a server fails to start due to missing dependencies, run npm install again.
Ensure port conflicts are avoided if the servers expose network interfaces; adjust configurations if needed. Configuration tips:
Keep both servers using the same DB_PATH for consistent data access if they share data structures.
Regularly back up the database file to prevent data loss during development.