Skip to main content
Glama
kanbanzone

Kanban Zone MCP Server

Official
by kanbanzone

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
KANBANZONE_API_KEYYesComposite credential accessId:apiKey. Generate in Org Settings → Integrations → API Key.
KANBANZONE_BASE_URLNoOverride only when pointing at a non-production environment.https://integrations.kanbanzone.io/v1

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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:

  • "Is my Kanban Zone connection working?"

  • "Which organization am I connected to?"

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):

  • include_members (boolean): include licensed and unlicensed member lists.

  • include_boards (boolean): include board summaries.

  • include_columns (boolean): include columns under each board (implies include_boards).

  • include_labels (boolean): include labels under each board (implies include_boards).

  • include_custom_fields (boolean): include workspace-level custom fields.

  • response_format ("markdown" | "json"): output format. Defaults to markdown.

Examples:

  • "List every board with its columns"

  • "Who are the members of this Kanban Zone workspace?"

kanbanzone_list_boardsA

List all boards in the organization with optional related data.

Args (all optional):

  • include_archived (boolean): include archived boards.

  • include_columns (boolean): include columns for each board.

  • include_labels (boolean): include labels for each board.

  • include_members (boolean): include member lists for each board.

  • include_custom_fields (boolean): include custom fields per board.

  • response_format ("markdown" | "json"): output format. Defaults to markdown.

Examples:

  • "What boards do I have?"

  • "Show me my boards including their columns"

kanbanzone_get_boardA

Fetch a single board by its publicId.

Args:

  • board (string, required): the board publicId, e.g. "OeMrbG8g".

  • include_columns (boolean): include columns.

  • include_labels (boolean): include labels.

  • include_members (boolean): include members.

  • include_custom_fields (boolean): include custom fields.

  • response_format ("markdown" | "json"): output format. Defaults to markdown.

Examples:

  • "Show me the OeMrbG8g board with its columns"

kanbanzone_list_board_columnsA

List board columns for a board.

Args:

  • board (string, required): the board publicId, e.g. "OeMrbG8g".

  • query: see schema.

  • include_default: see schema.

  • response_format ("markdown" | "json"): output format. Defaults to markdown.

Example: "List columns on the OeMrbG8g board"

kanbanzone_list_board_labelsA

List board labels for a board.

Args:

  • board (string, required): the board publicId, e.g. "OeMrbG8g".

  • response_format ("markdown" | "json"): output format. Defaults to markdown.

Example: "What labels are available on this board?"

kanbanzone_list_board_membersB

List board members for a board.

Args:

  • board (string, required): the board publicId, e.g. "OeMrbG8g".

  • response_format ("markdown" | "json"): output format. Defaults to markdown.

Example: "Who can I assign cards to on this board?"

kanbanzone_list_board_custom_fieldsA

List board custom fields for a board.

Args:

  • board (string, required): the board publicId, e.g. "OeMrbG8g".

  • response_format ("markdown" | "json"): output format. Defaults to markdown.

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:

  • board (string, required): board publicId.

  • title (string, required): card title.

  • description (string, optional): rich-text or plain description.

  • column (string, optional): column ObjectId. If omitted, the card lands in the default backlog.

  • owner (string, optional): account email of the assignee.

  • label (string, optional): label name (e.g. "Enhancement"). Must match a label configured on the board.

  • addToTop (boolean, optional): insert at the top of the column instead of the bottom.

Examples:

  • "Create a card titled 'Refactor auth' on board OeMrbG8g"

  • "Add a card to the To-Do column with description ..."

kanbanzone_list_cardsA

List cards on a board with optional filters and pagination.

Args:

  • board (string, required): board publicId.

  • columns (string, optional): comma-separated column ObjectIds to restrict to.

  • owner (string, optional): account ObjectId or email — only cards owned by this person.

  • label (string, optional): label ObjectId or description string.

  • days_since_last_update (number, optional): only cards untouched for N+ days.

  • include_archived (boolean, optional): include archived cards.

  • number (number, optional): fetch a single card by its #N number.

  • page (number, optional, default 1).

  • count (number, optional, default 20, max 100).

  • response_format ("markdown" | "json").

Examples:

  • "What cards are in progress on the OeMrbG8g board?"

  • "List my cards owned by alice@example.com"

kanbanzone_get_cardA

Fetch one card by its ObjectId.

Args:

  • id (string, required): card ObjectId.

  • board (string, optional): board publicId — required for mirror cards to disambiguate.

  • response_format ("markdown" | "json").

Examples:

  • "Show me card 6700aabbccddeeff00112233"

kanbanzone_update_cardA

Update fields on an existing card. Only included fields are changed.

Args:

  • id (string, required): card ObjectId.

  • board (string, optional): board publicId — required for mirror cards to disambiguate.

  • title (string, optional)

  • description (string, optional)

  • owner (string, optional): account email or ObjectId.

  • label (string, optional): label name (e.g. "Enhancement") or ObjectId.

  • dueAt (string, optional): ISO date or datetime.

  • customFields (array, optional): list of { label, value } pairs. label matches the custom-field name configured on the board.

Examples:

  • "Reassign card 670... to bob@example.com"

  • "Set the due date on card 670... to 2025-06-01"

  • "Set the Project Code custom field on card 670... to ABC-123"

kanbanzone_move_cardA

Move a card to a different column (and optionally a different board).

Args:

  • id (string, required): card ObjectId.

  • board (string, required): destination board publicId.

  • column (string, required): destination column ObjectId.

  • position (number, optional): 0-based position within the destination column.

Examples:

  • "Move card 670... to the In Progress column"

kanbanzone_get_card_historyA

Fetch the activity history for a card (column moves, edits, comments, etc.) starting from a date.

Args:

  • id (string, required): card ObjectId.

  • start (string, required): ISO date — only events on/after this date are returned.

  • response_format ("markdown" | "json").

Examples:

  • "What happened to card 670... since 2025-01-01?"

kanbanzone_get_card_metricsA

Fetch time-in-column and cycle/lead-time metrics for a card.

Args:

  • id (string, required): card ObjectId.

  • board (string, optional): board publicId — required for mirror cards.

  • response_format ("markdown" | "json").

Examples:

  • "How long has card 670... been in each column?"

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 board field to know which board to act on.

Args:

  • q (string, required): search text, minimum 2 characters.

  • board (string, optional): board publicId to narrow the search to one board. Omit to search across every board in the org.

  • include_archived (boolean, optional): include archived cards.

  • page (number, optional, default 1).

  • count (number, optional, default 20, max 100).

  • response_format ("markdown" | "json").

Examples:

  • "Search for cards mentioning billing"

  • "Find cards about webhook on the OeMrbG8g board"

kanbanzone_create_commentA

Add a comment to a card.

Args:

  • card (string, required): card ObjectId.

  • text (string, required): the comment body.

Examples:

  • "Add a comment to card 670... saying: blocked on design review"

kanbanzone_list_card_commentsA

List all comments on a card, oldest first.

Args:

  • id (string, required): card ObjectId.

  • response_format ("markdown" | "json").

Examples:

  • "What have people said on card 670...?"

kanbanzone_create_checklistA

Create a checklist on a card. Optionally pre-populate it with tasks in one call.

Args:

  • card (string, required): card ObjectId.

  • title (string, optional): checklist title.

  • checklistTemplate (string, optional): checklist template ObjectId.

  • tasks (array, optional): list of { description: string }. Task position is taken from array index — any position field on a task is ignored.

Examples:

  • "Add a checklist to card 670... with tasks: write tests, update docs"

  • "Apply checklist template 660... to card 670..."

kanbanzone_update_checklistA

Update title or position of a checklist on a card.

Args:

  • id (string, required): checklist ObjectId.

  • title (string, optional)

  • position (number, optional, ≥0)

Examples:

  • "Rename checklist 670... to 'QA tasks'"

  • "Move checklist 670... to position 0"

kanbanzone_list_card_checklistsA

List all checklists on a card, including their tasks.

Args:

  • id (string, required): card ObjectId.

  • response_format ("markdown" | "json").

Examples:

  • "What checklists are on card 670... and what's left to do?"

kanbanzone_create_taskA

Add a task to an existing checklist.

Args:

  • checklist (string, required): checklist ObjectId.

  • description (string, required): the task text.

  • position (number, optional, ≥0): if omitted, the task is appended.

  • dueAt (string, optional): ISO date.

  • owner (string, optional): account ObjectId or email.

Examples:

  • "Add a task 'Update README' to checklist 670..."

kanbanzone_update_taskA

Update fields on an existing task. Only included fields are changed.

Args:

  • id (string, required): task ObjectId.

  • description (string, optional)

  • completed (boolean, optional)

  • completedOn (string, optional): ISO date — only honoured when completed=true.

  • dueAt (string, optional): ISO date.

  • owner (string, optional): account ObjectId or email.

  • position (number, optional, ≥0)

Examples:

  • "Mark task 670... as complete"

  • "Reassign task 670... to alice@example.com"

kanbanzone_move_taskA

Move a task between checklists (or reorder within the same checklist).

Args:

  • id (string, required): task ObjectId.

  • checklistFrom (string, required): source checklist ObjectId.

  • checklistTo (string, required): destination checklist ObjectId. Pass the same value as checklistFrom to reorder in place.

  • position (number, required, ≥0): destination position.

Examples:

  • "Move task 670... from checklist A to checklist B at position 0"

kanbanzone_create_labelA

Create a label on a board. Each board can have at most one default label — setting is_default: true automatically clears the flag on any existing default label for the same board.

Args:

  • board (string, required): board publicId.

  • color (string, required): hex color, e.g. "#FF0000".

  • description (string, required): human-readable label text.

  • is_default (boolean, optional): mark this label as the board default.

  • position (number, optional): sort position. Defaults to end of the list.

Examples:

  • "Add an Urgent label to board OeMrbG8g with color #FF0000"

  • "Create a default Backlog label on board OeMrbG8g"

kanbanzone_get_labelA

Fetch one label by its ObjectId.

Args:

  • id (string, required): label ObjectId.

  • response_format ("markdown" | "json").

Examples:

  • "Show me label 670aabbccddeeff001122334"

kanbanzone_update_labelA

Update one or more fields on an existing label. Only included fields are changed.

Setting is_default: true automatically clears the flag on every other label on the same board. Setting is_default: false just unsets it — the board may end up with no default label.

Args:

  • id (string, required): label ObjectId.

  • color (string, optional): hex color, e.g. "#FF0000".

  • description (string, optional): human-readable label text.

  • is_default (boolean, optional): mark as board default (clears others).

  • position (number, optional): sort position.

Examples:

  • "Rename label 670... to High Priority"

  • "Make label 670... the default for its board"

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kanbanzone/kanban-zone-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server