KanbanFlow MCP Server
# KanbanFlow MCP Server
A Model Context Protocol (MCP) server for KanbanFlow - manage your boards, tasks, and workflows directly from Cursor/Claude.
## š Quick Start (One Command!)
### šÆ Recommended: Auto-Setup
```bash
# Install globally
npm install -g kanbanflow-mcp-server
# Auto-magic setup in ANY project
cd your-project-folder
kanbanflow-mcp-server --setup
```
**That's it!** ⨠The setup wizard will:
- š **Detect** your installation automatically
- š”ļø **Preserve** any existing MCP servers you have
- š¾ **Create backups** of your configuration
- āļø **Generate** the perfect config with full paths
- šÆ **Add** KanbanFlow to your Cursor setup
### š ļø Alternative: Developer Setup
```bash
# Clone and build from source
git clone https://github.com/williamavholmberg/kanbanflow-mcp-server
cd kanbanflow-mcp-server
npm install && npm run build
# Same magic setup wizard works here too!
kanbanflow-mcp-server --setup
```
## š Get Your API Token
1. Go to [kanbanflow.com/api](https://kanbanflow.com/api)
2. Create your API token
3. Enter it when prompted by the setup wizard
## š”ļø Safe & Smart Configuration
The setup wizard is **bulletproof**:
- ā
**Never overwrites** your existing MCP servers
- ā
**Creates automatic backups** before any changes
- ā
**Merges intelligently** with your current setup
- ā
**Uses reliable paths** (no binary issues)
- ā
**Works everywhere** (macOS, Windows, Linux)
### Example Scenarios:
**New project?**
```bash
š Creating new MCP configuration file...
ā
Setup complete!
```
**Already have MCP servers?**
```bash
š Found existing MCP configuration with 2 server(s)
ā Adding kanban-flow to existing configuration...
š¾ Created backup: mcp.json.backup.1692123456789
ā
Setup complete!
š” Your existing MCP servers are preserved!
```
**Updating KanbanFlow config?**
```bash
š Found existing MCP configuration with 3 server(s)
š Updating existing kanban-flow configuration...
š¾ Created backup: mcp.json.backup.1692123456789
ā
Setup complete!
```
## š ļø Available Tools
### Board Management
- **`get-board`** - Get your board structure and column IDs
- **`get-all-tasks`** - See all tasks across all columns
### Task Operations
- **`create-task`** - Create new tasks
- **`get-tasks`** - Get tasks from a specific column
- **`get-task-details`** - Get detailed task information
- **`update-task`** - Update task properties (name, column, color, etc.)
### Subtasks
- **`add-subtask`** - Add a subtask to any task
- **`update-subtask-by-position`** - Update subtasks by position
- **`add-subtasks`** - Add multiple subtasks at once
- **`create-task-with-subtasks`** - Create task + subtasks in one go
### Labels & Organization
- **`add-label`** - Add labels to tasks
- **`update-label`** - Update existing labels
- **`set-task-due-date`** - Set due dates
- **`update-custom-field`** - Update custom field values
### Comments
- **`add-comment`** - Add comments to tasks
- **`update-comment`** - Update existing comments
## š Usage Examples
Ask Claude things like:
- *"Show me my board structure"*
- *"Create a task called 'Fix bug' in the To-Do column"*
- *"Add subtasks to task T123: Write tests, Review code, Deploy"*
- *"Move task T456 to Done column"*
- *"What tasks are in my In Progress column?"*
- *"Create a task with 3 subtasks for implementing user authentication"*
## š§ Manual Configuration (Advanced)
If you prefer manual setup, the wizard generates this format:
```json
{
"mcpServers": {
"kanban-flow": {
"command": "node",
"args": ["/path/to/kanbanflow-mcp-server/build/index.js"],
"env": {
"KANBAN_API_TOKEN": "your_api_token_here"
}
}
}
}
```
## š Development
```bash
# Build
npm run build
# Help
kanbanflow-mcp-server --help
# Test (requires KANBAN_API_TOKEN env var)
npm run dev
```
## šÆ Why This MCP Server Rocks
- šŖ **One-command setup** - No manual config editing
- š”ļø **Bulletproof safety** - Never breaks your existing setup
- šÆ **Smart detection** - Works with any installation method
- š **Re-runnable** - Update your config anytime safely
- š± **Cross-platform** - macOS, Windows, Linux
- š **Industry-leading UX** - The way MCP setup should work
## š License
MIT License - see [LICENSE](LICENSE) file.
## š¤ Contributing
1. Fork the repo
2. Create your feature branch
3. Make your changes
4. Test with your KanbanFlow board
5. Submit a pull request
---
**Need help?** Open an issue!
> š” **Pro tip:** Run `kanbanflow-mcp-server --setup` anytime to update your configuration safely!TDQS
Scored across 16 tools
Each tool targets a specific action on a distinct resource (tasks, comments, labels, subtasks, board). Potential overlaps like add-subtask/add-subtasks and create-task/create-task-with-subtasks are clearly distinguished by complexity. The generic update-task is distinct from specific updates due to scope.
All tool names follow a consistent verb-noun pattern with hyphens (e.g., add-comment, get-task-details). Verbs are chosen appropriately and the structure is uniform across all 16 tools.
With 16 tools, the server covers a broad range of Kanban operations without being overwhelming. Each tool serves a clear purpose, and the count is well-suited for a board management domain.
The tool set lacks essential operations: no delete for tasks, comments, labels, or subtasks, and no ability to move tasks between columns. This creates significant gaps in completing typical Kanban workflows.