Kanban MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERVER_PORT | No | Port for the MCP server to listen on. | 3008 |
| PLANKA_BASE_URL | No | The base URL of the Planka instance. | http://localhost:3333 |
| PLANKA_AGENT_EMAIL | Yes | Email for the agent account to use with Planka. | |
| PLANKA_AGENT_PASSWORD | Yes | Password for the agent account. |
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 |
|---|---|
| mcp_kanban_project_board_managerC | Manage projects and boards with various operations (retrieve projects/boards, create, update, delete, or get board summary). Note: A board contains column lists of cards. |
| mcp_kanban_list_managerA | Manage kanban board lists/columns (columns/lanes on a board such as 'Backlog', 'To Do', 'In Progress', 'Done'). IMPORTANT: This manages top-level board columns containing cards. This is NOT for card task-lists (checklists) or individual sub-tasks inside cards. |
| mcp_kanban_card_managerB | Manage kanban cards (tickets/items inside board columns/lists). Supports creating, updating, moving, duplicating, deleting cards, and setting/updating card vertical position/order (lower numbers like 0, 65535 appear higher up at the top of the column, and higher numbers appear lower down at the bottom). Each card can contain its own checklist (task-list) with step-by-step tasks. |
| mcp_kanban_stopwatchC | Manage card stopwatches for time tracking |
| mcp_kanban_label_managerC | Manage kanban labels with various operations (create, update, delete, get_all, add_to_card, remove_from_card). Can add or remove single or multiple labels to/from a card at a time. |
| mcp_kanban_task_managerB | Manage step-by-step tasks (actionable checklist items with isCompleted boolean status) inside a card's checklist (task-list). Hierarchy: Board -> Board Column (List) -> Card -> Checklist (Task-List #1, #2...) -> Tasks (Individual checklist step items). A single card can contain multiple checklists, and each checklist contains multiple step tasks. |
| mcp_kanban_comment_managerC | Manage card comments with various operations |
| mcp_kanban_membership_managerC | Manage board memberships with various operations |
| mcp_kanban_batch_cardsA | Create multiple cards at once from a single JSON payload. Each card can include a description, vertical position, step-by-step checklist tasks (plain strings or {name, isCompleted} objects: task ∈ checklist ∈ card), labels (auto-created on the board if missing), and an optional comment — all in one call. |
| scheduler_list_labelsA | List all existing labels across all cards in the board(s) with card counts and state breakdowns (e.g. TODO, IN_PROGRESS, DONE). |
| mcp_kanban_list_labelsB | List all existing labels across all cards in the board(s) with card counts and state breakdowns (e.g. TODO, IN_PROGRESS, DONE). |
| scheduler_query_tasksB | Search and filter cards (and their checklist tasks/sub-tasks) across the Kanban board by criteria: cardId/taskId substring, labels (with matchMode any/all), keyword text in title/objective/description/allowed files, state (e.g. TODO, IN_PROGRESS, WAITING_REVIEW, WAITING_TEST, DONE), assignedPosition role, isReady, or isBlocked. |
| mcp_kanban_query_tasksA | Search and filter cards (and their checklist tasks/sub-tasks) across the Kanban board by criteria: cardId/taskId substring, labels (with matchMode any/all), keyword text in title/objective/description/allowed files, state (e.g. TODO, IN_PROGRESS, WAITING_REVIEW, WAITING_TEST, DONE), assignedPosition role, isReady, or isBlocked. |
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 13 tools
Several tools have overlapping or duplicated purposes: scheduler_list_labels and mcp_kanban_list_labels are identical, as are scheduler_query_tasks and mcp_kanban_query_tasks. Also, mcp_kanban_comment_manager and mcp_kanban_batch_cards both handle comments, and mcp_kanban_card_manager and mcp_kanban_task_manager might confuse agents about task vs card (though the hierarchy clarifies).
Naming is inconsistent: most tools use a 'mcp_kanban_' prefix with a manager suffix, but two are prefixed with 'scheduler_' and lack the manager suffix. Verbs vary (list vs get_all vs query), and there is a mix of 'batch_cards' and 'manager' patterns, breaking a predictable convention.
With 13 tools, the count is on the higher end, but the duplication (two pairs of identical tools) inflates the count. The server has a broad scope (boards, cards, labels, tasks, memberships, comments, batch operations) but could be consolidated to ~10-11 unique tools without losing functionality.
The tool surface covers most CRUD operations for boards, cards, labels, tasks, and memberships, plus batch creation and querying. Missing are operations like bulk updates or moves across lists, but the core lifecycle is present. However, with the duplicated query/list tools, the actual coverage of unique operations is thinner than it appears.