MCP Taskmanager

🚀 MCP Task Manager

The Model Context Protocol server is used for task management. This enables Claude Desktop (or any MCP client) to manage and execute tasks based on a queue system.

🚀 Quick Start (Users)

Prerequisites

• Node.js 18+ (Install via brew install node)
• Claude Desktop (Download and install from https://claude.ai/desktop)

Configuration

1. Open your Claude Desktop configuration file located at: ~/Library/Application Support/Claude/claude_desktop_config.json

You can find this file in the following way:

1. Open Claude Desktop.

2. Click "Claude" in the menu bar.

3. Click "Settings".

4. Click "Developer".

5. Add the following content to the configuration:

{
  "tools": {
    "taskmanager": {
      "command": "npx",
      "args": ["-y", "@kazuph/mcp-taskmanager"]
    }
  }
}

👨‍💻 For Developers

Prerequisites

• Node.js 18+ (Install via brew install node)
• Claude Desktop (Download and install from https://claude.ai/desktop)
• tsx (Install via npm install -g tsx)

Installation

git clone https://github.com/kazuph/mcp-taskmanager.git
cd mcp-taskmanager
npm install
npm run build

Development Configuration

1. Ensure that Claude Desktop is installed and running.

2. Install tsx globally if it is not already installed:

npm install -g tsx
# Or
pnpm add -g tsx

3. Modify your Claude Desktop configuration file located at: ~/Library/Application Support/Claude/claude_desktop_config.json

Add the following content to the MCP client configuration:

{
  "tools": {
    "taskmanager": {
      "args": ["tsx", "/path/to/mcp-taskmanager/index.ts"]
    }
  }
}

✨ Features

The task manager supports two main operational phases:

Planning Phase

• Accept a list of tasks (an array of strings) provided by the user.
• Store tasks internally as a queue.
• Return an execution plan (task overview, task ID, current queue status).

Execution Phase

• Return the next task from the queue upon request.
• Provide a feedback mechanism for task completion.
• Remove completed tasks from the queue.
• Prepare the next task for execution.

Parameters

• action: "plan" | "execute" | "complete"
• tasks: An array of task strings (required for the "plan" action).
• taskId: Task identifier (required for the "complete" action).
• getNext: A boolean flag to request the next task during the "execute" action.

💻 Usage Examples

Basic Usage

// Planning Phase
{
  action: "plan",
  tasks: ["Task 1", "Task 2", "Task 3"]
}

// Execution Phase
{
  action: "execute",
  getNext: true
}

// Complete a Task
{
  action: "complete",
  taskId: "task-123"
}