Skip to main content
Glama
letscodekrkumar

TaskTracker MCP Server

by letscodekrkumar
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

TaskTracker MCP Server

A DAG-based task tracking server for bug analysis and investigation workflows, built as a Model Context Protocol (MCP) server.

Features

  • DAG-based task dependencies — declare dependencies for structured investigation workflows

  • Circular dependency detection — automatic validation prevents invalid chains

  • Priority-based execution — tasks sorted by high/medium/low priority

  • Atomic bulk operations — add entire investigation plans in one call

  • Rich status tracking — pending → in_progress → completed / skipped / blocked

  • Evidence-based resolution — every resolved task requires a finding

  • Analysis gate — conclude_analysis() blocks until all tasks are resolved

Related MCP server: Task Crusader MCP

Installation

Option 1 — npx (no install needed)

npx tasktracker-mcp

Option 2 — Global install

npm install -g tasktracker-mcp
tasktracker-mcp

Option 3 — From source

git clone https://github.com/letscodekrkumar/tasktracker-mcp.git
cd tasktracker-mcp
npm install
npm run build
npm start

MCP Server Configuration

Claude Desktop

Edit claude_desktop_config.json:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Using npx (recommended):

{
  "mcpServers": {
    "tasktracker": {
      "command": "npx",
      "args": ["tasktracker-mcp"]
    }
  }
}

Using global install:

{
  "mcpServers": {
    "tasktracker": {
      "command": "tasktracker-mcp"
    }
  }
}

Using local source build:

{
  "mcpServers": {
    "tasktracker": {
      "command": "node",
      "args": ["/absolute/path/to/tasktracker-mcp/dist/index.js"]
    }
  }
}

Claude Code (CLI)

claude mcp add tasktracker npx tasktracker-mcp

Or with a local build:

claude mcp add tasktracker node /absolute/path/to/tasktracker-mcp/dist/index.js

Verify it connected:

claude mcp list
# tasktracker: npx tasktracker-mcp - ✓ Connected

Other MCP Clients

Any client that supports the MCP stdio transport can use:

{
  "command": "npx",
  "args": ["tasktracker-mcp"]
}

Tools

Tool

Purpose

add_task

Register a single task with optional dependencies

add_tasks_bulk

Register an entire investigation DAG atomically

update_task

Resolve task with evidence, update status, or rewire deps

get_ready_tasks

Get all executable tasks (deps resolved), priority-sorted

get_all_tasks

Full DAG snapshot with statuses, findings, and dependency state

conclude_analysis

Gate that blocks until all tasks resolved; returns summary

reopen_task

Reopen a blocked task when its blocker is resolved

reset

Clear all tasks and start fresh

Quick Start

# 1. Define your investigation DAG
add_tasks_bulk([
    {"title": "Fetch bug fields", "category": "log_check", "priority": "high"},
    {"title": "Extract machine ID", "category": "log_check", "priority": "high"},
    {"title": "Fetch run.log — search for TIMEOUT errors", "category": "log_check", "priority": "high", "depends_on": ["T2"]},
    {"title": "Identify root cause", "category": "root_cause", "priority": "high", "depends_on": ["T1", "T2", "T3"]}
])

# 2. Execute ready tasks
tasks = get_ready_tasks()  # returns T1, T2

# 3. Resolve tasks as you go
update_task("T1", status="completed", finding="Bug filed 2026-03-28. Build: 4.2.1-rc3.")
update_task("T2", status="completed", finding="Machine ID: X200-lot-7.")

# 4. T3 is now unblocked
update_task("T3", status="completed", finding="3 TIMEOUT errors at 14:22:01")

# 5. Conclude when all done
conclude_analysis()

Task Status Transitions

Transition

Allowed

Notes

pending → in_progress

Yes

No dependency check

pending/in_progress → completed

Yes

All deps must be resolved; finding required

pending/in_progress → skipped

Yes

Finding required

pending/in_progress → blocked

Yes

Finding required

completed / skipped → any

No

Permanently resolved

blocked → any

No

Use reopen_task() to reopen

Development

npm test              # run tests
npm run test:coverage # with coverage report
npm run build         # compile TypeScript
npm run dev           # build + run
npm run benchmark     # performance benchmarks

Project Structure

src/
  index.ts      # MCP server entry point
  tracker.ts    # DAG engine (task state, dependency resolution)
  types.ts      # TypeScript interfaces and validators
  monitor.ts    # Progress monitoring
  examples.ts   # Usage examples
  benchmark.ts  # Performance benchmarks
  __tests__/    # Test suite
docs/           # Design docs, deployment guide, specs

License

MIT — see LICENSE

Install Server
A
license - permissive license
A
quality
D
maintenance

How are these scores calculated?

Maintenance

–Maintainers
–Response time
–Release cycle
–Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Tools

Related MCP Servers

View all related MCP servers

Related MCP Connectors

  • PlanWright

    Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.

  • neverinfamous-memory-journal-mcp

    A MCP server built for developers enabling Git based project management with project and personal…

  • SmartBear MCP

    MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/letscodekrkumar/tasktracker-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server