Skip to main content
Glama
task-tracker-mcp

task-tracker-mcp

by feodal01

task-tracker-mcp

Description

task-tracker-mcp is a task management system for LLM-based agents. All tasks are stored in a single tree, available immediately after the server starts.

Related MCP server: Task Orchestration

Main Goal

Enable LLM agents to manage their tasks through a unified Task manager.

Requirements

  • Python 3.13 or higher

  • Node.js and npm (for @modelcontextprotocol/inspector)

Installation

Cloning the Repository

git clone git@github.com:feodal01/task-tracker-mcp.git
cd task-tracker-mcp

Setting Up the Environment

Configuration

Open the Claude Desktop configuration file located at:

On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json Add the following:

{
  "mcpServers": {
    "mcpServer": {
      "command": "uv",
      "args": [
        "--directory", 
        "/Path/to/task-tracker-mcp", 
        "run",
        "python",
        "-m",
        "mcp_server.mcp_service"
      ],
      "env": {
        "PYTHONPATH": "/Path/to/task-tracker-mcp/src"
      }
    }
  }
}

Running the Project

Starting the MCP Server

Using uv:

export PYTHONPATH=/Path/to/task-tracker-mcp/src
uv run python -m src.mcp_server.mcp_service

Starting the Inspector

To inspect the MCP server, use: uv:

npx @modelcontextprotocol/inspector uv --directory /Path/to/task-tracker-mcp run python -m mcp_server.mcp_service 

Running Tests

uv:

export PYTHONPATH=/Path/to/task-tracker-mcp/src
uv run pytest tests/

Running FastApi service with MCP tools

export PYTHONPATH=/Path/to/task-tracker-mcp/src
uv --directory /Path/to/task-tracker-mcp run python -m mcp_server.mcp_rest_service

License

This project is licensed under the MIT License — see the LICENSE file for details.

Contribution

Want to contribute? Fork the repository and submit a pull request.

Contacts

If you have any questions, contact me at: evgenyorlov1991@gmail.com

Available Tools

7 tools
create_taskA

Creates a new task (or subtask) in the single task tree. Args: description: Task description dod: Definition of Done (optional) deadline: Deadline (optional, ISO8601 string or datetime) assignee: Assignee (optional) parent_id: Parent task ID (if not specified, will be added to the root)

Inputs: description (required), dod, assignee, deadline, +1 more.

delete_taskC

Deletes a task. Args: task_id: Task ID

Inputs: task_id (required).

get_taskC

Retrieves information about a task. Args: task_id: Task ID

Inputs: task_id (required).

list_tasksA

Returns a list of all tasks in the tree (including subtasks).

Inputs: no named parameters.

test_toolA

Test function for checking MCP server health.

Inputs: no named parameters.

update_statusC

Closes a task. Args: task_id: Task ID status: Status (todo/done/cancelled/in_progress) reason: Close reason (optional)

Inputs: status (required), task_id (required), reason.

update_taskA
Updates an existing task. You can update any of the following fields:

Args:
    task_id (str): ID of the task to update.
    description (str, optional): New description for the task.
    dod (str, optional): New Definition of Done for the task.
    deadline (str, optional): New deadline for the task.
    assignee (str, optional): New assignee for the task.

Any combination of these fields can be provided. Only non-null values will be updated.

Inputs: task_id (required), dod, assignee, deadline, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action: create, update fields, update status, delete, get, list, and health check. There is no real overlap between updating task fields and updating task status.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern like create_task, update_task, delete_task, get_task, and list_tasks. Minor inconsistencies include update_status instead of update_task_status and the non-domain test_tool.

    Tool Count5/5

    Seven tools is well-scoped for a task tracker: core CRUD, status transitions, and listing are all covered without unnecessary redundancy. Each tool earns its place.

    Completeness4/5

    The surface covers create, read, update, delete, status changes, and listing, which is solid for basic task tracking. The main gap is the lack of an operation to move a task within the task tree after creation, since parent_id is only supported on create.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers