A
licenseNot graded
qualityD
maintenanceEnables AI assistants to manage Planka kanban boards, including creating, updating, and organizing tasks, lists, and cards via MCP.
15 npm
59
MIT
planka-mcp
by haliphax-ai
Related Servers
Alternatives to planka-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with Planka, a real-time Kanban board application, for managing projects, boards, lists, cards, and more.1021 npm5MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered project management by connecting Claude to Planka kanban boards via 75+ MCP tools for creating, updating, and managing projects, boards, lists, and cards.1GPL 3.0
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to interact with self-hosted Planka boards through the Planka REST API. It allows users to list, search, create, and update projects, boards, and cards using natural language.3-
- AlicenseAqualityFmaintenanceMCP server enabling AI agents to manage PLANKA kanban boards with full CRUD support for cards, tasks, labels, comments, and lists.1528 npm10MIT
- AlicenseAqualityBmaintenanceEnables Claude Code to control a Planka 2.x board via 15 MCP tools, with writes re-read and verified so reported success matches the board, plus an optional workflow that turns the board into durable agent memory.1539 npm2MIT
TDQS
C2.9/5.0
Scored across 56 tools
Disambiguation4/5
Most tools are clearly separated by resource and action, but some overlap exists: update_task can set completion while complete_task toggles it, and get_card_details bundles comments/tasks/labels that also have dedicated getters. Descriptions are clear enough to avoid major misselection.
Naming Consistency4/5
Tool names are predominantly snake_case verb_noun and easy to predict. Minor inconsistency: list-all operations use get_projects/get_boards but get_all_lists/get_all_cards/get_all_tasks, and there is no get_label single counterpart.
Tool Count1/5
56 tools is well above the 50+ extreme threshold for an MCP tool surface. Although the Planka domain has many entity types and each tool maps to a distinct operation, the sheer count will make agent tool selection unwieldy.
Completeness4/5
Core lifecycle coverage is strong across projects, boards, lists, cards, tasks, labels, comments, memberships, and stopwatch. Gaps include no attachment removal/update, no unassign parent-card operation, and no single-label getter, but these are minor compared to the covered surface.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive