Skip to content
Back to search

mcp-taskmanager

Model Context Protocol server for Task Management. This allows Claude Desktop (or any MCP client) to manage and execute tasks in a queue-based system.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/kazuph--mcp-taskmanager/badge.svg)](/listings/kazuph--mcp-taskmanager)

HTML

<a href="/listings/kazuph--mcp-taskmanager"><img src="/api/listings/kazuph--mcp-taskmanager/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Prerequisites

- Node.js 18+ (install via `brew install node`) - Claude Desktop (install from https://claude.ai/desktop)

Configuration

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

You can find this through the Claude Desktop menu: 1. Open Claude Desktop 2. Click Claude on the Mac menu bar 3. Click "Settings" 4. Click "Developer"

2. Add the following to your configuration:

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

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 121 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # MCP TaskManager
  2. Model Context Protocol server for Task Management. This allows Claude Desktop (or any MCP client) to manage and execute tasks in a queue-based system.
  3. <a href="https://glama.ai/mcp/servers/bdjh7kx05h"><img width="380" height="200" src="https://glama.ai/mcp/servers/bdjh7kx05h/badge" alt="@kazuph/mcp-taskmanager MCP server" /></a>
  4. ## Quick Start (For Users)
  5. ### Prerequisites
  6. - Node.js 18+ (install via `brew install node`)
  7. - Claude Desktop (install from https://claude.ai/desktop)
  8. ### Configuration
  9. 1. Open your Claude Desktop configuration file at:
  10. `~/Library/Application Support/Claude/claude_desktop_config.json`
  11. You can find this through the Claude Desktop menu:
  12. 1. Open Claude Desktop
  13. 2. Click Claude on the Mac menu bar
  14. 3. Click "Settings"
  15. 4. Click "Developer"
  16. 2. Add the following to your configuration:
  17. ```json
  18. {
  19. "tools": {
  20. "taskmanager": {
  21. "command": "npx",
  22. "args": ["-y", "@kazuph/mcp-taskmanager"]
  23. }
  24. }
  25. }
  26. ```
  27. ## For Developers
  28. ### Prerequisites
  29. - Node.js 18+ (install via `brew install node`)
  30. - Claude Desktop (install from https://claude.ai/desktop)
  31. - tsx (install via `npm install -g tsx`)
  32. ### Installation
  33. ```bash
  34. git clone https://github.com/kazuph/mcp-taskmanager.git
  35. cd mcp-taskmanager
  36. npm install
  37. npm run build
  38. ```
  39. ### Development Configuration
  40. 1. Make sure Claude Desktop is installed and running.
  41. 2. Install tsx globally if you haven't:
  42. ```bash
  43. npm install -g tsx
  44. # or
  45. pnpm add -g tsx
  46. ```
  47. 3. Modify your Claude Desktop config located at:
  48. `~/Library/Application Support/Claude/claude_desktop_config.json`
  49. Add the following to your MCP client's configuration:
  50. ```json
  51. {
  52. "tools": {
  53. "taskmanager": {
  54. "args": ["tsx", "/path/to/mcp-taskmanager/index.ts"]
  55. }
  56. }
  57. }
  58. ```
  59. ## Available Operations
  60. The TaskManager supports two main phases of operation:
  61. ### Planning Phase
  62. - Accepts a task list (array of strings) from the user
  63. - Stores tasks internally as a queue
  64. - Returns an execution plan (task overview, task ID, current queue status)
  65. ### Execution Phase
  66. - Returns the next task from the queue when requested
  67. - Provides feedback mechanism for task completion
  68. - Removes completed tasks from the queue
  69. - Prepares the next task for execution
  70. ### Parameters
  71. - `action`: "plan" | "execute" | "complete"
  72. - `tasks`: Array of task strings (required for "plan" action)
  73. - `taskId`: Task identifier (required for "complete" action)
  74. - `getNext`: Boolean flag to request next task (for "execute" action)
  75. ## Example Usage
  76. ```typescript
  77. // Planning phase
  78. {
  79. action: "plan",
  80. tasks: ["Task 1", "Task 2", "Task 3"]
  81. }
  82. // Execution phase
  83. {
  84. action: "execute",
  85. getNext: true
  86. }
  87. // Complete task
  88. {
  89. action: "complete",
  90. taskId: "task-123"
  91. }
  92. ```

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.