MCP Server for task management with specs, state machine, dependency graphs, and AI coaching
npm install @gofman3/task-master-mcp.gofman3/specs/ automatically
tasks.md updates on task/subtask completion
bash
npx @gofman3/task-master-mcp
`
MCP Config
`json
{
"mcpServers": {
"task-master": {
"command": "npx",
"args": ["@gofman3/task-master-mcp"]
}
}
}
`
Tools
$3
Spec management ā better than Kiro Specs.
Actions: create, get, list, update, delete, generate_tasks, progress, export
ā ļø CRITICAL: generate_tasks REQUIRES workspacePath!
`typescript
// Create spec with subtasks
task_spec({
action: 'create',
name: 'Auth Module',
requirements: [
{ id: 'REQ-1', userStory: 'As a user, I want to login', criteria: ['Email validation'] }
],
taskTemplates: [
{ content: 'Design API', priority: 1, subtasks: ['Define endpoints', 'Create schemas'] },
{ content: 'Implement login', dependsOn: ['t1'], priority: 2 },
{ content: 'Write tests', dependsOn: ['t2'], optional: true }
]
})
// Generate tasks + auto-export to .gofman3/specs/
task_spec({
action: 'generate_tasks',
specId: 'spec-xxx',
workspacePath: 'F:/Projects/my-app' // REQUIRED! Files created automatically
})
`
Export creates in .gofman3/specs/{spec-name}/:
- requirements.md ā User stories + acceptance criteria
- design.md ā Architecture + components + diagrams
- tasks.md ā Progress bar + grouped tasks + subtasks (auto-synced!)
- context.md ā #[[file:]] references for auto-load
$3
Task CRUD and state transitions.
Actions: add, update, delete, start, complete, complete_subtask, do, block, reopen, abandon
`typescript
// Complete a subtask (0-based index)
task_manage({ action: 'complete_subtask', taskId: 'xxx', subtaskIndex: 0 })
// When all subtasks done ā task auto-completes!
`
State Machine:
`
todo ā doing, abandoned
doing ā todo, blocked, done, abandoned
blocked ā todo, doing, abandoned
done ā todo (reopen)
`
$3
Visual task board.
Views: kanban, list, priority, mermaid
$3
Atomic batch creation with tempId references.
$3
AI-powered next task suggestion.
Auto-Sync
When you complete a task or subtask, tasks.md is automatically updated if workspacePath was provided during generate_tasks.
`markdown
Tasks: Auth Module
Progress: 1/3 (33%)
$3
- [x] 1. Design API
- [x] 1.1 Define endpoints
- [x] 1.2 Create schemas
$3
- [ ] 2. Implement login
`
License
MIT
---
šÆ How to Use (for humans)
$3
`
You: "Fix bug in auth.ts line 42"
AI: just does it, no extra steps
`
$3
Example prompt:
`
Working directory: C:/Projects/my-backend
1. Study folders src/auth/ and src/services/
2. use think_batch ā analyze architecture and edge cases
3. use task_spec ā create specification with tasks
Goal: "Implement JWT auth system with refresh tokens"
Requirements:
- Access token expires in 15 minutes
- Refresh token expires in 7 days
- Refresh token rotation on use
- Blacklist for revoked tokens
`
What happens:
1. AI studies project code
2. think_batch ā thinks through edge cases (what if token stolen? race condition on rotation?)
3. task_spec ā creates spec in .gofman3/specs/jwt-auth/:
`
.gofman3/specs/jwt-auth/
āāā requirements.md ā what we're building (user stories)
āāā design.md ā how we're building (architecture)
āāā tasks.md ā progress tracking (auto-updates!)
āāā context.md ā file references
`
$3
`
Show task_board
`
`
āāāāāāāāāāāāāāā¬āāāāāāāāāāāāāā¬āāāāāāāāāāāāāā
ā TODO ā DOING ā DONE ā
āāāāāāāāāāāāāāā¼āāāāāāāāāāāāāā¼āāāāāāāāāāāāāā¤
ā [P2] Tests ā [P1] Token ā [P1] Routes ā
ā ā Service ā ā
āāāāāāāāāāāāāāā“āāāāāāāāāāāāāā“āāāāāāāāāāāāāā
`
$3
`
use task_recommend
`
AI tells you which task to pick (by priority + dependencies).
$3
When working on task with subtasks ā they get checked off automatically, tasks.md updates:
`markdown
- [x] 1. Setup routes
- [x] 1.1 POST /login
- [x] 1.2 POST /refresh
- [ ] 1.3 POST /logout ā current
``