Kanban MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KANBAN_DATA_DIR | No | Directory to store the database. Defaults to ~/.kanban-mcp/. |
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 |
|---|---|
| kanban_list_projectsA | List available projects |
| kanban_get_boardA | Fetch the full board for a project, including columns and tickets. All tickets include completionSummary field (populated for completed tickets). |
| kanban_find_ticketA | Look up a single ticket with project, column, and epic context. Returns full ticket details including completionSummary for completed tickets. |
| kanban_get_ticket_runsA | Fetch append-only run history for a ticket, including events and artifacts for each run. |
| kanban_get_batchC | Fetch a Kanban batch with its planned ticket items. |
| kanban_staging_lease_statusA | Inspect the shared staging lease without revealing its secret holder token. |
| kanban_staging_lease_acquireA | Atomically acquire the one shared staging lease for a ticket candidate. Build the immutable preview before calling this. If another holder is active, acquired is false and no token is returned. |
| kanban_staging_lease_assertC | Validate the holder token and fencing generation immediately before a staging alias change, migration, shared-fixture mutation, acceptance, or rollback. |
| kanban_staging_lease_heartbeatA | Extend an active staging lease while targeted hosted UAT is still running. An expired or superseded holder cannot renew. |
| kanban_staging_lease_releaseA | Release the staging lease after the candidate is accepted or the previous immutable deployment is restored. A stale fencing generation cannot release a successor lease. |
| kanban_find_column_ticketsA | Filter tickets within a column by priority band. Supply priorities or priorityMin/priorityMax bounds. |
| kanban_search_ticketsC | Search tickets in a project with optional filters and pagination. |
| kanban_column_top_ticketC | Return the highest-priority ticket (lowest priority value) from a column. |
| kanban_create_projectB | Create a new project with optional custom column names |
| kanban_create_columnC | Add a new column to a project |
| kanban_rename_columnB | Rename or update metadata for a column by id |
| kanban_delete_columnA | Delete a column by id (removes contained tickets) |
| kanban_create_ticketC | Create a new ticket in a project column |
| kanban_update_ticketA | Update ticket fields such as title, description, column, estimate, epic, or completion summary. When moving a ticket to Done, provide completionSummary with: 1) What was done, 2) Future improvements, 3) Separated work (links to related tickets). Deployment proof is optional. |
| kanban_move_ticketA | Move a ticket to another column. When moving to Done, provide completionSummary with: 1) What was done, 2) Future improvements, 3) Separated work (links to related tickets). Deployment proof is optional. |
| kanban_link_docC | Associate a documentation path with a ticket. |
| kanban_list_doc_linksB | Retrieve documentation links associated with a ticket. |
| kanban_list_ticket_linksB | Find all tickets referencing a documentation path. |
| kanban_reorder_column_ticketsA | Set the vertical order for tickets in a column. First ticket in the list receives priority 0. |
| kanban_set_estimateC | Assign a Scrum poker estimate to a ticket |
| kanban_delete_ticketC | Delete a ticket by id |
| kanban_list_epicsA | List all epics for a project |
| kanban_create_epicC | Create a new epic in a project |
| kanban_update_epicC | Update epic name, description, or color |
| kanban_delete_epicC | Delete an epic by id |
| kanban_get_metricsB | Fetch burn-up, burndown, and velocity metrics for a project |
| kanban_list_scrum_valuesA | Return the allowed Scrum poker estimate values |
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 32 tools
Most tools map cleanly to distinct resource-action pairs, but kanban_update_ticket and kanban_move_ticket both allow moving tickets and updating completion summaries, which creates possible confusion. The two doc-link tools also have inverse orientations that could be mistaken for each other.
Names follow a mostly consistent kanban_verb_noun pattern, but kanban_column_top_ticket lacks a verb and find/search are used interchangeably. Overall, the convention is predictable and readable.
With 32 tools, the surface is heavy and exceeds the comfortable range for an agent to quickly select between operations. Many tools are individually reasonable, but the count feels bloated for a kanban server, especially with niche entries like kanban_list_scrum_values and kanban_get_batch.
Core CRUD/lifecycle coverage exists for projects, columns, tickets, epics, doc links, and the staging lease. Notable gaps include no project update/delete, no doc-link removal, and no batch mutators, but agents can work around most of these.