Skip to main content
Glama
Kanban Zone MCP Server

Kanban Zone MCP Server

Official
by kanbanzone

Kanban Zone MCP Server

Model Context Protocol server that lets AI assistants (Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, and any MCP client) drive your Kanban Zone workspace via the public API.

33 tools across boards, cards, comments, links, attachments, checklists, tasks, and labels. The only delete is unlinking two cards.

Two ways to connect. The hosted server at https://mcp.kanbanzone.io/mcp is the recommended option for every client, Claude Desktop included — paste the URL, sign in with your Kanban Zone account, done. Nothing to install, no API key to manage, and you always get the current tool set. The local install (this npm package) runs the same server on your own machine over stdio — for stdio-only clients, unattended setups like CI where a browser sign-in isn't possible, restricted networks, or developing against a fork.

What you can do

  • Read your boards, columns, labels, members, and custom fields.

  • Create, list, get, update, move, and search cards.

  • Inspect a card's history and time-in-column metrics.

  • Create, get, and update labels.

  • Add comments.

  • Link cards as parent and child or predecessor and successor, change a link's type, and unlink them.

  • List a card's attachments and get a download link for one.

  • Create, update, and list checklists — including bulk task creation in a single call.

  • Create, update, and move tasks.

Related MCP server: sanban

Claude Desktop: open Settings → Connectors → Add custom connector, paste https://mcp.kanbanzone.io/mcp, and click Connect. A browser window opens to sign in to Kanban Zone and approve access — the tools then appear in the tool picker. No config file, no API key.

Claude Code:

claude mcp add --transport http kanbanzone https://mcp.kanbanzone.io/mcp

Sign in when prompted. Where a browser sign-in isn't possible, the hosted server also accepts an API key as a header: Authorization: Bearer accessId:apiKey.

Local install (Claude Desktop)

Prefer the hosted quick start above. Use a local install when your client is stdio-only, your setup is unattended (an API key in an env var beats a browser sign-in there), your network blocks mcp.kanbanzone.io, or you're developing against a fork.

  1. Get an API key. In Kanban Zone: Settings → Integrations → API Keys. Copy the whole thing — it looks like accessId:apiKey.

  2. Edit your config.

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%\Claude\claude_desktop_config.json

    {
      "mcpServers": {
        "kanbanzone": {
          "command": "npx",
          "args": ["-y", "kanban-zone-mcp-server"],
          "env": {
            "KANBANZONE_API_KEY": "accessId:apiKey"
          }
        }
      }
    }
  3. Restart Claude Desktop. The Kanban Zone tools appear in the tool picker.

  4. Try it. Ask Claude: "Is my Kanban Zone connection working?" — Claude calls kanbanzone_get_me and replies with your org name.

Local install (Claude Code)

claude mcp add kanbanzone \
  -e KANBANZONE_API_KEY=accessId:apiKey \
  -- npx -y kanban-zone-mcp-server

Configuration

Environment variables for the local server:

Variable

Required

Default

Description

KANBANZONE_API_KEY

yes

—

Composite credential accessId:apiKey. Generate in Settings → Integrations → API Keys.

KANBANZONE_BASE_URL

no

https://integrations.kanbanzone.io/v1

Override only when pointing at a non-production environment.

The server validates the key on startup. A missing or malformed value (no : separator) exits immediately with a message pointing at the org settings page.

Tools

33 tools, all prefixed with kanbanzone_:

Group

Tools

Organization & Auth

get_me, get_organization

Boards

list_boards, get_board, list_board_columns, list_board_labels, list_board_members, list_board_custom_fields

Cards

create_card, list_cards, get_card, update_card, move_card, get_card_history, get_card_metrics, search_cards

Comments

create_comment, list_card_comments

Links

list_card_links, create_card_link, update_card_link, delete_card_link

Attachments

list_card_attachments, get_card_attachment

Checklists

create_checklist, update_checklist, list_card_checklists

Tasks

create_task, update_task, move_task

Labels

create_label, get_label, update_label

User-facing docs with example prompts: https://docs.kanbanzone.io/mcp. Full input/output schemas: https://docs.kanbanzone.io/api.

Prompts

Three user-invocable prompts ship alongside the tools: Board Review, Checklist Generator, and Standup Summary. In Claude Code they register as slash commands; in Claude Desktop they appear in the prompt picker. For clients without native MCP prompt support, PROMPTS.md carries the same texts as copy-paste blocks.

Running from source

If you'd rather run from a local clone (development, contributions, custom modifications):

git clone https://github.com/kanbanzone/kanban-zone-mcp-server.git
cd kanban-zone-mcp-server
npm install
KANBANZONE_API_KEY=accessId:apiKey node src/index.js

Plain JavaScript — no compile step.

Troubleshooting

401 on every tool call. If you connected with an API key, it's wrong or expired — regenerate it. If you signed in to the hosted server, disconnect it in your client and connect again for a fresh token.

Tools don't appear in the client. Confirm the path is correct and the client was restarted after editing config. For npx installs, run npx -y kanban-zone-mcp-server once manually to make sure it downloads cleanly.

Card does not exist on a card you can see. It's a mirror — pass board=<publicId> to disambiguate which mirror.

Truncation warnings on list_cards. Paginate with page / count, or narrow with columns, owner, label, or daysSinceLastUpdate.

Security

The local server runs on your machine. It does not transmit data to any third-party AI service — every API call goes directly to https://integrations.kanbanzone.io. Your API key never leaves your machine except as an Authorization: Basic header on those direct calls.

The hosted server is operated by Kanban Zone and talks to that same public API. Signing in uses OAuth and makes a user-level connection: your client holds an access token tied to your account, the tools reach what your account can reach, and changes are attributed to your name. An API key is an org-level credential — it acts as the organization's integration identity and by default reaches every board in the org (keys can be scoped to chosen boards when generated).

License

MIT.

Available Tools

27 tools
kanbanzone_create_cardCreate a 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 ..."

Inputs: board (required), title (required), description, column, +3 more.

kanbanzone_create_checklistCreate a checklist on a cardA

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..."

Inputs: card (required), title, checklistTemplate, tasks.

kanbanzone_create_commentCreate a comment on a cardA

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"

Inputs: card (required), text (required).

kanbanzone_create_labelCreate a label on a boardA

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"

Inputs: board (required), color (required), description (required), is_default, +1 more.

kanbanzone_create_taskCreate a task in a checklistA

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..."

Inputs: checklist (required), description (required), position, dueAt, +1 more.

kanbanzone_get_boardGet a boardA
Read-onlyIdempotent

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"

Inputs: board (required), include_columns, include_labels, include_members, +2 more.

kanbanzone_get_cardGet a cardA
Read-onlyIdempotent

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"

Inputs: id (required), board, response_format.

kanbanzone_get_card_historyGet card historyA
Read-onlyIdempotent

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?"

Inputs: id (required), start (required), response_format.

kanbanzone_get_card_metricsGet card metricsA
Read-onlyIdempotent

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?"

Inputs: id (required), board, response_format.

kanbanzone_get_labelGet a labelA
Read-onlyIdempotent

Fetch one label by its ObjectId.

Args:

  • id (string, required): label ObjectId.

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

Examples:

  • "Show me label 670aabbccddeeff001122334"

Inputs: id (required), response_format.

kanbanzone_get_meGet current organization (auth check)A
Read-onlyIdempotent

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?"

Inputs: response_format.

kanbanzone_get_organizationGet organization contextA
Read-onlyIdempotent

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?"

Inputs: include_members, include_boards, include_columns, include_labels, +2 more.

kanbanzone_list_board_columnsList board columnsA
Read-onlyIdempotent

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"

Inputs: board (required), query, include_default, response_format.

kanbanzone_list_board_custom_fieldsList board custom fieldsA
Read-onlyIdempotent

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?"

Inputs: board (required), response_format.

kanbanzone_list_board_labelsList board labelsA
Read-onlyIdempotent

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?"

Inputs: board (required), response_format.

kanbanzone_list_board_membersList board membersB
Read-onlyIdempotent

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?"

Inputs: board (required), response_format.

kanbanzone_list_boardsList boardsA
Read-onlyIdempotent

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"

Inputs: include_archived, include_columns, include_labels, include_members, +2 more.

kanbanzone_list_card_checklistsList checklists on a cardA
Read-onlyIdempotent

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?"

Inputs: id (required), response_format.

kanbanzone_list_card_commentsList comments on a cardA
Read-onlyIdempotent

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...?"

Inputs: id (required), response_format.

kanbanzone_list_cardsList cards on a boardA
Read-onlyIdempotent

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"

Inputs: board (required), columns, owner, label, +6 more.

kanbanzone_move_cardMove a cardA
Idempotent

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"

Inputs: id (required), board (required), column (required), position.

kanbanzone_move_taskMove a task to another checklistA
Idempotent

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"

Inputs: id (required), checklistFrom (required), checklistTo (required), position (required).

kanbanzone_search_cardsSearch cards by title or numberA
Read-onlyIdempotent

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"

Inputs: q (required), board, include_archived, page, +2 more.

kanbanzone_update_cardUpdate a cardA
Idempotent

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"

Inputs: id (required), board, title, description, +4 more.

kanbanzone_update_checklistUpdate a checklistA
Idempotent

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"

Inputs: id (required), title, position.

kanbanzone_update_labelUpdate a labelA
Idempotent

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"

Inputs: id (required), color, description, is_default, +1 more.

kanbanzone_update_taskUpdate a taskA
Idempotent

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:

Inputs: id (required), description, completed, completedOn, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 27 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers