看板管理协议服务器

// Create a checklist with tasks in one operation
kanban-mcp_kanban_task_manager({
  action: "create_tasklist_with_tasks",
  cardId: "card_id_here",
  name: "Testing Checklist",
  tasks: [
    { name: "□ Run unit tests" },
    { name: "□ Run integration tests" },
    { name: "□ Update documentation" }
  ]
})

// Get all task lists for a card
kanban-mcp_kanban_task_manager({
  action: "get_all",
  cardId: "card_id_here"
})

// Create a comment
kanban-mcp_kanban_comment_manager({
  action: "create",
  cardId: "card_id_here",
  text: "Implementation complete, ready for review"
})

// Get all comments
kanban-mcp_kanban_comment_manager({
  action: "get_all",
  cardId: "card_id_here"
})

// Create a card
kanban-mcp_kanban_card_manager({
  action: "create",
  listId: "list_id_here",
  name: "New Feature",
  description: "Implement new feature X"
})

// Move a card within the same board
kanban-mcp_kanban_card_manager({
  action: "move",
  id: "card_id_here",
  listId: "target_list_id",
  position: 0  // Optional: defaults to end of list (65535)
})

// Move a card to a different board
kanban-mcp_kanban_card_manager({
  action: "move",
  id: "card_id_here",
  listId: "target_list_id",
  boardId: "target_board_id",  // REQUIRED when moving between boards
  position: 0  // Optional
})

// Move a card to a different project
kanban-mcp_kanban_card_manager({
  action: "move",
  id: "card_id_here",
  listId: "target_list_id",
  boardId: "target_board_id",  // REQUIRED
  projectId: "target_project_id",  // REQUIRED when moving between projects
  position: 0  // Optional
})

// Get card details with related data
kanban-mcp_kanban_card_manager({
  action: "get_details",
  cardId: "card_id_here"
})

// Add label to card
kanban-mcp_kanban_label_manager({
  action: "add_to_card",
  cardId: "card_id_here",
  labelId: "label_id_here"
})

📋 BACKLOG BOARD                        📊 WORKLOG BOARD
├── Architecture (ARCH-xxx)            ├── Planned (ready to build)
├── Security (SEC-xxx)                 ├── In Progress (actively working)
├── Performance (PERF-xxx)             ├── Testing (awaiting verification)
└── Feature (FEAT-xxx)                 └── Completed (done)

# Kanban Workflow with MCP

## Board Structure
- **Backlog Board** (ID: `your_backlog_board_id`)
  - Lists: Architecture, Security, Performance, Feature
  - Issues with priority labels only (Critical/High/Normal)
  
- **Worklog Board** (ID: `your_worklog_board_id`)
  - Lists: Planned, In Progress, Testing, Completed
  - Issues with priority labels (status = which list they're in)

## Workflow Phases

### 1️⃣ Creating New Issues
When discovering work that needs to be done:
1. Create card in appropriate Backlog board list (Architecture/Security/Performance/Feature)
2. Add priority label: Critical/High/Normal
3. Write brief description of the issue
4. Get card URL and track in your project documentation

**Example:**
```javascript
// Create security issue in Backlog
kanban-mcp_kanban_card_manager({
  action: "create",
  listId: "security_list_id",
  name: "SEC-001: Missing rate limiting on login endpoint",
  description: "Login endpoint vulnerable to brute force attacks"
})

// Add priority label
kanban-mcp_kanban_label_manager({
  action: "add_to_card",
  cardId: "new_card_id",
  labelId: "critical_label_id"
})

// Update card description with plan
kanban-mcp_kanban_card_manager({
  action: "update",
  id: "card_id",
  description: "## Implementation Plan\n\n### Summary\n..."
})

// Move to Planned list
kanban-mcp_kanban_card_manager({
  action: "move",
  id: "card_id",
  listId: "planned_list_id",
  boardId: "worklog_board_id"
})

// Add comment
kanban-mcp_kanban_comment_manager({
  action: "create",
  cardId: "card_id",
  text: "Plan created on 2026-01-30"
})

// Move to In Progress
kanban-mcp_kanban_card_manager({
  action: "move",
  id: "card_id",
  listId: "in_progress_list_id"
})

// Add progress comment
kanban-mcp_kanban_comment_manager({
  action: "create",
  cardId: "card_id",
  text: "✅ Phase 1 complete: Database schema updated"
})

// When implementation done, move to Testing
kanban-mcp_kanban_card_manager({
  action: "move",
  id: "card_id",
  listId: "testing_list_id"
})

// CRITICAL: Add testing checklist
kanban-mcp_kanban_task_manager({
  action: "create_tasklist_with_tasks",
  cardId: "card_id",
  name: "Testing",
  tasks: [
    { name: "Verify feature works as expected" },
    { name: "Run npm run build (confirm success)" },
    { name: "Run npm run test (confirm passing)" },
    { name: "Manual testing of edge cases" },
    { name: "Verify no regressions" },
    { name: "Update documentation if needed" }
  ]
})

---

### Real-World Example

Here's how an AI assistant would handle the complete lifecycle:

---

### Benefits

✅ **Transparent Progress** - All stakeholders see real-time status in Planka  
✅ **AI-Readable Context** - AI reads cards to understand current state  
✅ **Async Collaboration** - Team can edit cards, AI syncs before working  
✅ **Audit Trail** - Comments and task lists document the journey  
✅ **Testing Accountability** - Explicit checklist before marking complete  

---

## 🔧 Available Tools

| Tool | Description |
|------|-------------|
| `mcp_kanban_project_board_manager` | Manage projects and boards |
| `mcp_kanban_list_manager` | Manage board lists |
| `mcp_kanban_card_manager` | Manage cards |
| `mcp_kanban_task_manager` | Manage task lists and tasks |
| `mcp_kanban_label_manager` | Manage labels |
| `mcp_kanban_comment_manager` | Manage card comments |
| `mcp_kanban_membership_manager` | Manage board memberships |
| `mcp_kanban_stopwatch` | Track time on cards |

---

## 📝 What's New in This Version?

### Planka 2.0 API Compatibility (2026-01-30)

**Fixed Issues:**
- ✅ Updated task lists endpoints (`/api/cards/:cardId/task-lists`)
- ✅ Added support for individual tasks within task lists (`/api/task-lists/:taskListId/tasks`)
- ✅ Fixed comments endpoints (`/api/cards/:cardId/comments` instead of `/comment-actions`)
- ✅ All API endpoints verified against Planka 2.0.0-rc.4 routes

**New Features:**
- 🆕 `create_tasklist_with_tasks` - Create checklist with items in one call
- 🆕 Individual task management functions
- 🆕 Simplified comment operations
- 🆕 Comprehensive documentation

**Breaking Changes from Original:**
- Task list creation now correctly uses `/task-lists` endpoint
- Comments require `cardId` for retrieval
- All endpoints updated to match Planka 2.0 API structure

---

## 🏗️ Architecture

### Planka 2.0 Data Model

### Key Concepts

**Task Lists vs Tasks:**
- **Task List** = A checklist on a card (e.g., "Testing Checklist")
- **Task** = An individual checkbox item within a task list (e.g., "✓ Run tests")

**Comments vs Actions:**
- **Comments** = User-created comments on cards
- **Actions** = Activity log (includes comments + system events)

---

## 🧪 Development

### Running Tests
```bash
npm test

npm run build

npm run dev

# Projects & Boards
GET    /api/projects
POST   /api/projects/:projectId/boards
GET    /api/boards/:id

# Lists & Cards
POST   /api/boards/:boardId/lists
POST   /api/lists/:listId/cards
GET    /api/cards/:id

# Task Lists & Tasks
POST   /api/cards/:cardId/task-lists
POST   /api/task-lists/:taskListId/tasks
PATCH  /api/task-lists/:id
PATCH  /api/tasks/:id

# Comments
GET    /api/cards/:cardId/comments
POST   /api/cards/:cardId/comments
PATCH  /api/comments/:id

# Labels
POST   /api/boards/:boardId/labels
POST   /api/cards/:cardId/card-labels
DELETE /api/cards/:cardId/card-labels/labelId::labelId

# Memberships
POST   /api/boards/:boardId/board-memberships
PATCH  /api/board-memberships/:id