mcp_kanban_card_manager
Manage kanban cards with various operations
LABSCO SUMMARY
Board objects are addressed by type, and the operation rides in an action parameter rather than in the tool name.
That keeps the surface flat for a board API this wide — projects, boards, lists, cards, tasks, task lists, labels, comments, memberships and the stopwatch are each addressed by name — at the cost of the operation being a value you pass rather than a name you pick. Work that lands on a card can be done without a second lookup: assignment accepts an email or a username instead of a Planka user ID, and a board read can bring comments and task details with it. Everything runs as the account in PLANKA_AGENT_EMAIL, so board history attributes the changes to that agent rather than to the person asking.
What it is
A Planka client covering 10 tools, split by the board object each works on, talking to a Planka instance as a service account.
What you get
- The board structure itself: mcp_kanban_project_board_manager for projects and boards including background type and gradient, and mcp_kanban_list_manager for the lists on a board with name, color and position.
- Cards with their contents in one place: mcp_kanban_card_manager covers name, description, dueDate, list and project placement, position, isCompleted and isClosed, with mcp_kanban_comment_manager for the discussion on the card.
- Checklists that match Planka v2.0: mcp_kanban_task_list_manager for the task lists on a card and mcp_kanban_task_manager for the tasks inside them, each with a position and a completion flag.
- People on the work: mcp_kanban_membership_manager sets board membership with a role and a canComment flag, and mcp_kanban_card_membership_manager assigns users to a card by ID, email or username.
- Labels and elapsed time: mcp_kanban_label_manager for label name, color and position, and mcp_kanban_stopwatch for the time tracked against a card.
- Detail pulled with the board rather than after it: the project and board tool takes page and perPage for paging, and includeComments and includeTaskDetails to bring card detail back in the same response.
Requirements
A reachable Planka instance and an account for the agent to act as: PLANKA_BASE_URL, PLANKA_AGENT_EMAIL, PLANKA_AGENT_PASSWORD and PLANKA_IGNORE_SSL.
Setup effort
One command plus credentials — npx -y @navyatec/planka-v2-mcp@latest, then supply credentials
USE CASES
01
Standing up a board for a new project without leaving the editor
Create the project and its board, lay out the lists in order, and define the labels the team will sort by.
02
Moving a card through the workflow with its checklist intact
Reposition the card into the next list, then work the task lists and tasks on it rather than rewriting the description each time.
03
Handing work to a teammate who is not in your user-ID lookup table
Assign the card by email or username, set what the person can do on the board, and leave the context as a comment on the card itself.
04
Measuring how long a card really sat in progress
Run the card's stopwatch alongside the work instead of reconstructing the time afterwards from the board history.
10 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
mcp_kanban_card_membership_manager
Manage memberships of a card (assign users by ID, email, or username)
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_list_manager
Manage task lists with various operations (Planka v2.0)
mcp_kanban_task_manager
Manage kanban tasks with various operations
BEFORE YOU INSTALL
What to know first
Tools you get
10 tools when we connected. Each tool is a manager covering many operations; get_board, update_board, delete_board, get_board_summary and get_project_summary are operations of mcp_kanban_project_board_manager, not tools. Nine of the ten write.
Requires
- npx on PATH
- PLANKA_AGENT_EMAIL in your environment
- PLANKA_AGENT_PASSWORD in your environment
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 10 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @navyatec/planka-v2-mcp@latestMCP Clients
Cursor, Claude Desktop, Antigravity
JSON
{
"mcpServers": {
"planka-mcp": {
"command": "npx",
"args": [
"-y",
"@navyatec/planka-v2-mcp@latest"
],
"env": {
"PLANKA_BASE_URL": "<YOUR_PLANKA_BASE_URL>",
"PLANKA_AGENT_EMAIL": "<YOUR_PLANKA_AGENT_EMAIL>",
"PLANKA_AGENT_PASSWORD": "<YOUR_PLANKA_AGENT_PASSWORD>",
"PLANKA_IGNORE_SSL": "true"
}
}
}
}
