KanbanFlow MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KANBAN_API_TOKEN | Yes | Your KanbanFlow API token from https://kanbanflow.com/api |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-boardC | Get Kanban board structure |
| create-taskC | Create a new task on the board |
| get-tasksB | Get all tasks in a column |
| get-task-detailsC | Get detailed information about a specific task by its ID |
| update-taskC | Update properties of an existing task |
| get-all-tasksA | Get all tasks from all columns on the board |
| add-subtaskB | Add a subtask to an existing task |
| update-subtask-by-positionB | Update a subtask by its position in the subtask list |
| add-labelB | Add a label to an existing task |
| update-labelA | Update an existing label on a task by finding it by name |
| set-task-due-dateC | Set or update a due date for a task |
| update-custom-fieldB | Set or update a custom field value on a task |
| add-commentB | Add a comment to an existing task |
| update-commentB | Update an existing comment on a task |
| add-subtasksB | Add multiple subtasks to an existing task in one operation |
| create-task-with-subtasksB | Create a new task and add multiple subtasks to it in one operation |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.