Kanban Zone MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KANBANZONE_API_KEY | Yes | Composite credential accessId:apiKey. Generate in Org Settings → Integrations → API Key. | |
| KANBANZONE_BASE_URL | No | Override only when pointing at a non-production environment. | https://integrations.kanbanzone.io/v1 |
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 |
|---|---|
| kanbanzone_get_meA | Verify the configured API key works and return the organization name. Use this first when troubleshooting setup — if it returns the org name, auth is working. Returns: { success: true, name: } Examples:
|
| kanbanzone_get_organizationA | Fetch the organization profile, with optional related data: members, boards, columns, labels, and custom fields. Useful for orienting an agent at session start ("what does this workspace look like?"). Args (all optional):
Examples:
|
| kanbanzone_list_boardsA | List all boards in the organization with optional related data. Args (all optional):
Examples:
|
| kanbanzone_get_boardA | Fetch a single board by its publicId. Args:
Examples:
|
| kanbanzone_list_board_columnsA | List board columns for a board. Args:
Example: "List columns on the OeMrbG8g board" |
| kanbanzone_list_board_labelsA | List board labels for a board. Args:
Example: "What labels are available on this board?" |
| kanbanzone_list_board_membersB | List board members for a board. Args:
Example: "Who can I assign cards to on this board?" |
| kanbanzone_list_board_custom_fieldsA | List board custom fields for a board. Args:
Example: "What custom fields does this board have?" |
| kanbanzone_create_cardA | Create a single card on a board. Internally calls the batch POST /cards endpoint with a one-card array. Args:
Examples:
|
| kanbanzone_list_cardsA | List cards on a board with optional filters and pagination. Args:
Examples:
|
| kanbanzone_get_cardA | Fetch one card by its ObjectId. Args:
Examples:
|
| kanbanzone_update_cardA | Update fields on an existing card. Only included fields are changed. Args:
Examples:
|
| kanbanzone_move_cardA | Move a card to a different column (and optionally a different board). Args:
Examples:
|
| kanbanzone_get_card_historyA | Fetch the activity history for a card (column moves, edits, comments, etc.) starting from a date. Args:
Examples:
|
| kanbanzone_get_card_metricsA | Fetch time-in-column and cycle/lead-time metrics for a card. Args:
Examples:
|
| kanbanzone_search_cardsA | Full-text search across cards in your organization. Matches card titles and card numbers. Task, comment, and attachment text are not searched in this version. Results are sorted by relevance (best match first). Mirror cards: results are returned per (card, board) pair — a card mirrored to two
boards that matches the query appears twice, each with that board's bucket, label,
owner, and watchers. Use the returned Args:
Examples:
|
| kanbanzone_create_commentA | Add a comment to a card. Args:
Examples:
|
| kanbanzone_list_card_commentsA | List all comments on a card, oldest first. Args:
Examples:
|
| kanbanzone_create_checklistA | Create a checklist on a card. Optionally pre-populate it with tasks in one call. Args:
Examples:
|
| kanbanzone_update_checklistA | Update title or position of a checklist on a card. Args:
Examples:
|
| kanbanzone_list_card_checklistsA | List all checklists on a card, including their tasks. Args:
Examples:
|
| kanbanzone_create_taskA | Add a task to an existing checklist. Args:
Examples:
|
| kanbanzone_update_taskA | Update fields on an existing task. Only included fields are changed. Args:
Examples:
|
| kanbanzone_move_taskA | Move a task between checklists (or reorder within the same checklist). Args:
Examples:
|
| kanbanzone_create_labelA | Create a label on a board. Each board can have at most one default label —
setting Args:
Examples:
|
| kanbanzone_get_labelA | Fetch one label by its ObjectId. Args:
Examples:
|
| kanbanzone_update_labelA | Update one or more fields on an existing label. Only included fields are changed. Setting Args:
Examples:
|
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 27 tools
Most tools have distinct purposes (create vs update vs move), but some overlap exists between get_board with include options and the specific list_* tools (e.g., list_board_columns). Descriptions help differentiate, but an agent might occasionally pick the wrong one.
All tools follow a consistent snake_case pattern of kanbanzone_<verb>_<noun>, with verbs like create, get, list, update, move, search. No mixing of conventions, making it predictable.
27 tools is slightly above the typical well-scoped range (3-15), but it comprehensively covers the Kanban domain. The count feels heavy but not excessive given the complexity of the application.
The tool surface covers most core CRUD operations for cards, checklists, tasks, labels, and comments, but notably lacks delete operations for any entity and has no board creation/update/delete or column management. This leaves agents unable to fully manage lifecycle.