mcp_kanban_card_manager
Manage kanban cards with various operations
LABSCO SUMMARY
The board updates while you are still talking about the work.
Eight tools cover the whole of Planka because each one takes an action rather than splitting create, read, update and delete into separate entries. It connects as a named account, so every card and comment it makes is attributed to that account.
What it is
An MCP server for Planka, the self-hosted Kanban board. Eight manager tools each cover one object type and take an action, so the whole board is reachable through a small surface.
What you get
- Projects and boards created, listed and managed
- Lists managed within a board, including their position
- Cards created, moved, duplicated and organised, with descriptions and tasks
- Tasks and subtasks created and marked complete
- Coloured labels created and applied to cards
- Comments added to cards
- Per-card stopwatches for time tracking
- Board memberships, roles and comment permissions
Requirements
Three environment variables: PLANKA_BASE_URL for your instance, which defaults to a local address, plus PLANKA_AGENT_EMAIL and PLANKA_AGENT_PASSWORD for the account it acts as. Node — npm install, then npm run build.
Setup effort
One command plus credentials — npx @grec0/mcp-planka@latest, then supply credentials
USE CASES
01
Turning a conversation into cards
Create the cards in the right list, with descriptions and subtasks already filled in.
02
Moving work across the board as it progresses
Move the card to the next list without opening Planka.
03
Setting up a board for a new project
Create the project and board, then the lists it needs, in position order.
04
Recording time against a task
Start and stop the card's stopwatch as you work.
05
Leaving context on a card for the next person
Add the comment to the card itself rather than in chat.
06
Organising a board that grew unreadable
Apply coloured labels, and check who has access to what.
8 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
mcp_kanban_comment_manager
Manage card comments with various operations
mcp_kanban_label_manager
Manage kanban labels with various operations
mcp_kanban_list_manager
Manage kanban lists with various operations
mcp_kanban_membership_manager
Manage board memberships with various operations
mcp_kanban_project_board_manager
Manage projects and boards with various operations
mcp_kanban_stopwatch
Manage card stopwatches for time tracking
mcp_kanban_task_manager
Manage kanban tasks with various operations
BEFORE YOU INSTALL
What to know first
Tools you get
8 tools when we connected. Each tool is a manager that takes an action parameter (get_projects, create_board, card moves), so eight names hide dozens of operations. The documentation is in Spanish.
Requires
- npx on PATH
- Node.js >=18.0.0
- PLANKA_AGENT_EMAIL in your environment
- PLANKA_AGENT_PASSWORD in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 8 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @grec0/mcp-planka@latestMCP Clients
Claude Desktop — npx
CLAUDE DESKTOP — NPX · JSON
{
"mcpServers": {
"planka": {
"command": "npx",
"args": [
"@grec0/mcp-planka@latest"
],
"env": {
"PLANKA_BASE_URL": "http://localhost:3000",
"PLANKA_AGENT_EMAIL": "demo@demo.demo",
"PLANKA_AGENT_PASSWORD": "demo"
}
}
}
}Claude Desktop — local build
CLAUDE DESKTOP — LOCAL BUILD · TERMINAL
git clone https://github.com/gcorroto/mcp-planka.git
cd mcp-planka
npm install
npm run buildCLAUDE DESKTOP — LOCAL BUILD · JSON
{
"mcpServers": {
"planka": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_PLANKA>/dist/index.js"
],
"env": {
"PLANKA_BASE_URL": "http://localhost:3000",
"PLANKA_AGENT_EMAIL": "demo@demo.demo",
"PLANKA_AGENT_PASSWORD": "demo"
}
}
}
}Use the absolute path to dist/index.js inside your clone.
