MCP Task Manager Server

🚀 MCP Task Manager Server

The MCP Task Manager Server is a Node.js-based tool designed to manage and manipulate task data. It provides services by implementing a set of tools defined in the MCP protocol, including creating, updating, deleting tasks, and related operations.

🚀 Quick Start

Prerequisites

• Node.js (LTS version is recommended)
• npm

Install Dependencies

npm install

Run in Development Mode

npm run dev

In development mode, the server will automatically load code changes (via nodemon) and print logs to the standard output. By default, the log file will be written to ./data/taskmanager.db.

Build for Production

npm run build

Run in Production

npm start

✨ Features

Supported Task Operations

• Create new tasks
• Update existing tasks
• Delete tasks along with their subtasks and dependencies
• Read the task list
• Export/import task data

Database Management

• Use an SQLite database to store task data, with the default path being ./data/taskmanager.db.
• Support configuring the database path via the environment variable (DATABASE_PATH).

Logging

• Provide different levels of log output (debug, info, warn, error).
• The default log level is info, which can be modified via the environment variable LOG_LEVEL.

Tool Implementation

• Each task operation has a corresponding utility class and parameter validation (using the Zod library).

📦 Installation

Prerequisites

• Node.js (LTS version recommended)
• npm

Install Dependencies

npm install

💻 Usage Examples

Basic Usage

To start the server in development mode:

npm run dev

In development mode, the server will automatically load code changes (via nodemon) and print logs to the standard output.

Advanced Usage

To run the server in production mode, first build the project:

npm run build

Then start the server:

npm start

📚 Documentation

Configuration

Database Path

• You can modify the default SQLite database path by setting the DATABASE_PATH environment variable. For example:

DATABASE_PATH=./mydb.db npm run dev

Log Level

• Set the log output level via the LOG_LEVEL environment variable. Valid values are: debug, info, warn, error. For example:

LOG_LEVEL=debug npm run dev

Project Structure

MCP-TaskManager/
├── src/
│   ├── config/                  # Configuration management module
│   ├── db/                      # Database-related code (including schema.sql)
│   ├── repositories/            # Data access layer (SQLite operations)
│   ├── services/                # Core business logic implementation
│   ├── tools/                   # MCP tool definitions (Params.ts and Tool.ts)
│   ├── types/                  # Shared TypeScript interfaces
│   └── utils/                 # Utility functions for logging, error handling, etc.
├── dist/                       # Compiled JavaScript output directory
├── docs/                      # Documentation and specification files (PRD, RFC, etc.)
├── data/                     # Default SQLite database storage path (automatically created)
└── tasks.md                   # Development task tracking file

Code Style and Quality Management

Code Formatting

• Use prettier to format the code to ensure consistency and readability.
• Configuration files: .eslintrc.json, .prettierrc.json

Static Code Checking

• Use ESLint and TypeScript for code quality checking.
• During development, automatic checking is implemented via Husky and lint-staged.

Unit Testing

• Complete unit test cases are provided (located in the src/test/ directory).
• You can run the tests using the following command:

npm test

🔧 Technical Details

Project Goals

1. Provide a reliable task management tool that supports complex task dependencies and subtask structures.
2. Implement the interfaces defined in the MCP protocol to ensure compatibility with other systems.
3. Ensure the maintainability and extensibility of the code for future feature enhancements.

Use Cases

• Personal Task Management: Users can create, update, and delete tasks via the command line or graphical interface.
• Team Collaboration Tool: Supports multiple users operating simultaneously (requires an authentication module).
• Automation Processes: Integrate into other systems via API calls to automate tasks.

Next Steps

1. Install dependencies and start the server:

npm install && npm run dev

2. View the default log output or database file.
3. Modify the configuration environment variables as needed.

For more detailed information, please refer to the project documentation and code implementation.