Kanbanize
Kanbanize is designed to help advanced product teams apply the principles of Lean and Kanban to their work to maximize results.
Verdict
Common use cases
- Update card statuses during standup
- Add blockers and comments from Slack threads
- Triage support tickets into Kanban lanes
- Check milestone progress before planning meetings
- Archive completed cards after sprint review
Integration
- Vendor
- Kanbanize
- Category
- productivity
- Auth
- API_KEY
- Tools
- 24
- Composio slug
kanbanize
Tools
- Add a comment to a card
Tool to add a comment to a Kanbanize card. Use when you need to add notes, updates, or any text-based information to an existing card.
- Check Board Milestone
Tool to check if a milestone is available on the specified board. Use when you need to verify milestone existence on a specific board. Returns True if the milestone is available (HTTP 204), False if not found (HTTP 404).
- Check User Is Card Watcher
Tool to check if a user is a watcher of a specific card. Use when you need to verify if a user is watching a card.
- Delete Boarddestructive
Tool to delete a board by its ID. Use when you need to permanently remove a board from Kanbanize. Note: The board must be archived before deletion.
- Delete Carddestructive
Tool to delete a card from the Kanbanize board. Use when you need to permanently remove a card and all its associated data from the board.
- Delete Tagdestructive
Tool to delete a tag from Kanbanize. Use when removing a tag and optionally replacing it with another tag for all affected cards.
- Delete Workflowdestructive
Tool to delete a workflow for the specified board. Use when you need to permanently remove a workflow from a board.
- Get Board Block Reasons
Tool to get a list of block reasons available on a board. Use when you need to retrieve available block reasons for a specific board.
- Get Board Card Templates
Tool to retrieve a list of card templates available on a Kanbanize board. Use when you need to see what card templates are configured for a specific board.
- Get Child Cards
Tool to retrieve a list of child cards for a specified parent card. Use when you need to view all cards that are children of a given parent card in the Kanbanize hierarchy.
- Get Column
Tool to get the details of a specific column from a Kanbanize board. Use when you need to retrieve column information such as name, WIP limit, card ordering, or workflow configuration.
- Get Columns
Tool to get a list of columns for a specific board in Kanbanize. Use when you need to retrieve all columns configured for a board, including their workflow assignments, positions, limits, and display settings.
- Get Custom Fields
Tool to retrieve a list of custom fields from Kanbanize with optional filtering. Use when you need to fetch custom field definitions, filter by field IDs, name, availability level, enabled status, types, or retrieve additional details like
- Get Stickers
Tool to retrieve a list of stickers with optional filtering by sticker IDs, label, availability, and enabled status. Use when you need to fetch stickers from Kanbanize to apply to cards or to view available stickers in the system.
- Get User
Tool to get the details of a specified user in Kanbanize. Use when you need to retrieve information about a user such as their username, email, real name, avatar, enabled status, language preferences, timezone, and other attributes.
- Get workflow cycle time columns
Tool to retrieve workflow's cycle time columns from a Kanbanize board. Use when you need to identify which columns are included in cycle time calculations for a specific workflow.
- Get Workspace Data Fields
Tool to retrieve a list of data fields available on a workspace. Use when you need to fetch all custom data fields configured for a specific Kanbanize workspace.
- Remove Board Block Reasondestructive
Tool to make a block reason unavailable on a board. Use when you need to remove a specific block reason from a board's available options.
- Remove Child Carddestructive
Tool to remove the link between a parent card and a child card. Use when you need to unlink a child card from its parent card in Kanbanize.
- Set card block reason
Tool to block a Kanbanize card by setting a block reason. Use when you need to mark a card as blocked and specify the reason preventing progress.
- Update Board Sticker
Tool to update the properties of a sticker for the specified board. Use when you need to modify usage limits for a sticker on a board or card.
- Update Data Field Workspaces
Tool to add, update, or remove a data field on one or more workspaces via batch operations. Use when you need to configure data field availability and settings across multiple workspaces.
- Update Lane Default Setting
Tool to update the default value of a specific lane setting in Kanbanize. Use when you need to modify default settings for a lane on a board.
- Update Tag
Tool to update the specified tag in Kanbanize. Use when you need to modify tag properties like label, color, availability, or enabled status.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations tab. 2. Click 'Add Integration' and select Kanbanize from the list. 3. Log into your Kanbanize account and go to Settings > API to generate a new API key. 4. Copy the key and paste it into Switchy's connection dialog, then click 'Connect'. 5. Switchy will verify the key and list your accessible boards. 6. To test the connection, open any Space and type '@Kanbanize list cards on board [your board name]' — you should see a summary of active cards. 7. From now on, @mention Kanbanize in any message to invoke its tools: add comments, move cards between columns, check blockers, or delete outdated tasks.
What teammates see: by default, memories from Kanbanize are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Standup Card Summary
@Kanbanize list all cards in the 'In Progress' column on the Engineering board and summarize their titles and assignees.Open in a Space →
Add Blocker Comment
@Kanbanize add a comment to card #1234 saying 'Blocked by API rate limit issue — waiting on vendor response'.Open in a Space →
Check Milestone Status
@Kanbanize check if the 'Q1 Launch' milestone is available on the Product board.Open in a Space →
Move Card to Done
@Kanbanize move card #5678 to the 'Done' column and add a comment that testing passed.Open in a Space →
List Block Reasons
@Kanbanize get the list of block reasons available on the Operations board.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@kanbanize show me all blocked cards on the Engineering board and explain why each one is stuck
Found 4 blocked cards on the Engineering board: 1. "API rate limiting implementation" — blocked by "Waiting on infrastructure team" (assigned to Sarah, in Development column) 2. "Mobile app crash fix" — blocked by "Missing reproduction steps" (assigned to Mike, in QA column) 3. "Database migration script" — blocked by "Awaiting security review" (no assignee, in Review column) 4. "User onboarding redesign" — blocked by "Dependency on marketing assets" (assigned to Lisa, in Design column) This is an illustrative example showing how Kanbanize surfaces blockers. Your actual board state will vary.
This example combines card retrieval with block-reason lookup to surface workflow bottlenecks. Requires read access to the specified board. Kanbanize's block-reason taxonomy is board-specific, so the reasons shown here reflect what your team has configured. Useful for daily standups or sprint retrospectives.
@kanbanize move the "Payment gateway integration" card to the Testing column and add a comment that QA can start validation
Card "Payment gateway integration" moved to Testing column. Added comment: "QA can start validation — all acceptance criteria met, staging environment updated with latest build." This illustrative example shows a typical handoff action. The card's workflow position and comment history are now updated in Kanbanize. Team members watching this card will receive notifications per their settings.
Demonstrates write operations that change card state and add audit trail. Requires API key with write permissions. Moving cards between columns may trigger workflow automation rules you've configured (e.g., auto-assigning QA lead, sending Slack notifications). Always verify the target column exists on your board before moving cards.
@kanbanize list all cards tagged "technical-debt" across our boards, group them by estimated effort, and draft a prioritization proposal for next quarter
Found 12 cards tagged "technical-debt" across 3 boards: **High effort (5+ days):** 4 cards including database schema refactor, legacy API sunset, monolith decomposition. **Medium effort (2-4 days):** 5 cards including test coverage gaps, dependency upgrades, logging improvements. **Low effort (<2 days):** 3 cards including code style fixes, documentation updates, dead code removal. **Prioritization proposal:** Start next quarter with the 3 low-effort wins to build momentum, then tackle the medium-effort logging and test coverage work to reduce operational friction before attempting high-effort architectural changes. This illustrative example shows how cross-board tag queries enable portfolio-level planning.
Showcases the MCP's ability to aggregate data across multiple boards and synthesize it with AI reasoning. Tag-based queries require consistent tagging discipline across your organization. Effort estimates must exist as card properties in Kanbanize for grouping to work. This workflow is powerful for quarterly planning but assumes your boards use standardized effort fields.
Use-case deep-dives
When Kanbanize MCP beats manual board updates for client work
A 6-person creative agency runs weekly ops reviews where the account lead walks through 40-60 active client cards across three boards. Before Switchy, the lead spent 15 minutes per meeting manually updating card statuses, adding block reasons, and tagging cards for follow-up. With the Kanbanize MCP, the AI reads current board state, suggests status moves based on Slack context from the week, and bulk-applies tags or comments while the team discusses. The 24-tool scope covers the full card lifecycle—add comments, check watchers, delete stale cards, manage block reasons. This works because the agency's boards are stable (under 200 cards each) and the API key auth is simple to rotate quarterly. If your boards exceed 500 cards or you need sub-board permissions, the MCP's flat auth model will frustrate you. For small-team ops cadences, this is the fastest path from conversation to board truth.
Where Kanbanize MCP falls short for cross-functional planning
A 10-person product team uses Kanbanize to hand off sprint work from design to engineering. The product manager wants the AI to auto-create cards from Figma links, assign them to the next workflow stage, and notify watchers. The Kanbanize MCP handles the card creation and workflow moves, but it can't bridge to Figma or trigger Slack notifications—those require separate MCPs or custom webhooks. The result is a half-automated handoff: the AI drafts cards and sets milestones, but the PM still manually pastes Figma URLs and pings engineers. This scenario sits at the threshold. If your handoff is purely within Kanbanize (moving cards, adding comments, checking block reasons), the MCP delivers. If you need multi-tool orchestration, you'll spend more time wiring integrations than the MCP saves. For single-tool workflows inside Kanbanize, it's a clean win.
When Kanbanize MCP speeds up support-to-eng triage
A 4-person support team triages 20-30 customer issues daily in Kanbanize, escalating 5-8 to engineering each week. The support lead uses Switchy to scan new cards, check if users are already watchers, add escalation tags, and post triage notes—all from a single chat thread. The Kanbanize MCP's 'Check User Is Card Watcher' and 'Add a comment to a card' tools let the AI handle the repetitive lookup-and-tag loop without the lead switching tabs. The workflow stays fast because the board is under 300 cards and the team only needs read-write on cards, not board-level admin. If your support volume exceeds 50 cards per day or you need real-time webhook triggers, the MCP's polling-based updates will lag. For daily triage at small-team scale, this cuts 10 minutes off every standup.
Frequently asked
What does the Kanbanize MCP let me do in Switchy?
It connects your Kanbanize boards so AI agents can read and update cards, add comments, check milestones, manage tags, and delete workflows or boards. You can ask an agent to summarise blocked cards, add a comment to a specific card, or verify if a user is watching something — all without leaving Switchy's chat interface.
Do I need admin access to connect Kanbanize?
You need a Kanbanize API key, which typically requires account-level permissions to generate. If your team restricts API key creation to admins or board owners, you'll need their help to set this up. The key grants access to all boards and cards the associated user can see in Kanbanize.
Can the MCP create new Kanbanize boards or workflows?
No. The 24 tools focus on reading board data and modifying existing cards, comments, tags, and milestones. You can delete boards and workflows, but creation happens in Kanbanize directly. If you need to spin up a new board, do it in the Kanbanize UI first, then reference it via the MCP.
How is this different from using Kanbanize's web app?
The MCP lets you query and update cards conversationally — ask an agent to find all blocked cards with a specific tag, or add a comment to three cards at once. The web app is faster for visual board management and drag-drop workflows; the MCP is faster for bulk reads, cross-board queries, and integrating Kanban data into broader AI workflows.
Who on the team should connect the Kanbanize MCP?
Whoever owns the API key. That person's Kanbanize permissions determine what the MCP can see and change. If you want the agent to access private boards or delete workflows, connect it under an admin account. For read-only use cases, a standard user key works fine.