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
Detailed security scan evidence is not public for this MCP yet. Public identity, registry metadata, and independently observed protocol inventory remain available.
Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.
Version 1.1.1 declares 1 executable entrypoint.
npm install --save-exact @kazuph/mcp-taskmanager@1.1.1npx -y -p @kazuph/mcp-taskmanager@1.1.1 mcp-taskmanager{
"mcpServers": {
"@kazuph/mcp-taskmanager": {
"command": "npx",
"args": [
"-y",
"-p",
"@kazuph/mcp-taskmanager@1.1.1",
"mcp-taskmanager"
]
}
}
}| Canonical slug | kazuph-mcp-taskmanager-1a08463f | Deployment | Local Only |
|---|---|---|---|
| Canonical package | npm:@kazuph/mcp-taskmanager | Repository | kazuph/mcp-taskmanager |
| First published | — | Latest release | — |
| Last security verification | — | Classification confidence | 90% |
| Publication | Draft | Official distribution | Not verified |
| Channel | Identifier | Current version | Versions | Source |
|---|---|---|---|---|
| npm | @kazuph/mcp-taskmanager | 1.1.1 | 5 | Repository |
| Package | Version | Published / observed | Inventory | Security scan |
|---|---|---|---|---|
| npm@kazuph/mcp-taskmanager | 1.1.1Current | Sep 5, 2026 | 10 toolsSucceeded · 0 resources · 0 prompts | Evidence restricted |
Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.
No public current-version evidence is available yet.
| Tool | Category | Annotations | Risk |
|---|---|---|---|
add_tasks_to_requestAdd new tasks to an existing request. This allows extending a request with additional tasks.
A progress table will be displayed showing all tasks including the newly added ones.Input schema{
"type": "object",
"properties": {
"requestId": {
"type": "string"
},
"tasks": {
"type": "array",
"items": {
"type": "object",
"properties": {
"title": {
"type": "string"
},
"description": {
"type": "string"
}
},
"required": [
"title",
"description"
]
}
}
},
"required": [
"requestId",
"tasks"
]
} | — | — | |
approve_request_completionAfter all tasks are done and approved, this tool finalizes the entire request. The user must call this to confirm that the request is fully completed.
A progress table showing the final status of all tasks will be displayed before requesting final approval.
If not approved, the user can add new tasks using 'request_planning' and continue the process.Input schema{
"type": "object",
"properties": {
"requestId": {
"type": "string"
}
},
"required": [
"requestId"
]
} | — | — | |
approve_task_completionOnce the assistant has marked a task as done using 'mark_task_done', the user must call this tool to approve that the task is genuinely completed. Only after this approval can you proceed to 'get_next_task' to move on.
A progress table will be displayed before requesting approval, showing the current status of all tasks.
If the user does not approve, do not call 'get_next_task'. Instead, the user may request changes, or even re-plan tasks by using 'request_planning' again.Input schema{
"type": "object",
"properties": {
"requestId": {
"type": "string"
},
"taskId": {
"type": "string"
}
},
"required": [
"requestId",
"taskId"
]
} | — | — | |
delete_taskDelete a specific task from a request. Only uncompleted tasks can be deleted.
A progress table will be displayed showing the remaining tasks after deletion.Input schema{
"type": "object",
"properties": {
"requestId": {
"type": "string"
},
"taskId": {
"type": "string"
}
},
"required": [
"requestId",
"taskId"
]
} | — | — | |
get_next_taskGiven a 'requestId', return the next pending task (not done yet). If all tasks are completed, it will indicate that no more tasks are left and that you must wait for the request completion approval.
A progress table showing the current status of all tasks will be displayed with each response.
If the same task is returned again or if no new task is provided after a task was marked as done but not yet approved, you MUST NOT proceed. In such a scenario, you must prompt the user for approval via 'approve_task_completion' before calling 'get_next_task' again. Do not skip the user's approval step.
In other words:
- After calling 'mark_task_done', do not call 'get_next_task' again until 'approve_task_completion' is called by the user.
- If 'get_next_task' returns 'all_tasks_done', it means all tasks have been completed. At this point, you must not start a new request or do anything else until the user decides to 'approve_request_completion' or possibly add more tasks via 'request_planning'.Input schema{
"type": "object",
"properties": {
"requestId": {
"type": "string"
}
},
"required": [
"requestId"
]
} | — | — | |
list_requestsList all requests with their basic information and summary of tasks. This provides a quick overview of all requests in the system.Input schema{
"type": "object",
"properties": {}
} | — | — | |
mark_task_doneMark a given task as done after you've completed it. Provide 'requestId' and 'taskId', and optionally 'completedDetails'.
After marking a task as done, a progress table will be displayed showing the updated status of all tasks.
After this, DO NOT proceed to 'get_next_task' again until the user has explicitly approved this completed task using 'approve_task_completion'.Input schema{
"type": "object",
"properties": {
"requestId": {
"type": "string"
},
"taskId": {
"type": "string"
},
"completedDetails": {
"type": "string"
}
},
"required": [
"requestId",
"taskId"
]
} | — | — | |
open_task_detailsGet details of a specific task by 'taskId'. This is for inspecting task information at any point.Input schema{
"type": "object",
"properties": {
"taskId": {
"type": "string"
}
},
"required": [
"taskId"
]
} | — | — | |
request_planningRegister a new user request and plan its associated tasks. You must provide 'originalRequest' and 'tasks', and optionally 'splitDetails'.
This tool initiates a new workflow for handling a user's request. The workflow is as follows:
1. Use 'request_planning' to register a request and its tasks.
2. After adding tasks, you MUST use 'get_next_task' to retrieve the first task. A progress table will be displayed.
3. Use 'get_next_task' to retrieve the next uncompleted task.
4. **IMPORTANT:** After marking a task as done, the assistant MUST NOT proceed to another task without the user's approval. The user must explicitly approve the completed task using 'approve_task_completion'. A progress table will be displayed before each approval request.
5. Once a task is approved, you can proceed to 'get_next_task' again to fetch the next pending task.
6. Repeat this cycle until all tasks are done.
7. After all tasks are completed (and approved), 'get_next_task' will indicate that all tasks are done and that the request awaits approval for full completion.
8. The user must then approve the entire request's completion using 'approve_request_completion'. If the user does not approve and wants more tasks, you can again use 'request_planning' to add new tasks and continue the cycle.
The critical point is to always wait for user approval after completing each task and after all tasks are done, wait for request completion approval. Do not proceed automatically.Input schema{
"type": "object",
"properties": {
"originalRequest": {
"type": "string"
},
"splitDetails": {
"type": "string"
},
"tasks": {
"type": "array",
"items": {
"type": "object",
"properties": {
"title": {
"type": "string"
},
"description": {
"type": "string"
}
},
"required": [
"title",
"description"
]
}
}
},
"required": [
"originalRequest",
"tasks"
]
} | — | — | |
update_taskUpdate an existing task's title and/or description. Only uncompleted tasks can be updated.
A progress table will be displayed showing the updated task information.Input schema{
"type": "object",
"properties": {
"requestId": {
"type": "string"
},
"taskId": {
"type": "string"
},
"title": {
"type": "string"
},
"description": {
"type": "string"
}
},
"required": [
"requestId",
"taskId"
]
} | — | — |
| Endpoint | Transport | Authentication | Health | Observed |
|---|---|---|---|---|
| No verified remote endpoint is linked. | ||||
Install the selected package version with: npm install --save-exact @kazuph/mcp-taskmanager@1.1.1
@kazuph/mcp-taskmanager MCP Server exposed 10 tools during independent protocol observation, including add_tasks_to_request, approve_request_completion, approve_task_completion, delete_task, get_next_task, list_requests, mark_task_done, open_task_details, and others.
The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.
Curated product and capability guides containing this catalog record.