F
licenseNot graded
qualityB
maintenanceEnables AI agents to claim task cards from a self-hosted board, receive complete briefings, and submit handoffs with evidence and telemetry for human validation.
1
-
planka-mcp
by KT-SPARKS
Related Servers
Alternatives to planka-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI agents to interact with Planka-based Kanban boards, including managing boards, lists, cards, checklists, tasks, comments, and labels through an agent-friendly MCP interface.1322 npmMIT
- AlicenseBqualityCmaintenanceEnables AI agents to manage tasks through a board with backlog, ready, in-progress, and done columns, plan daily work, track velocity, forecast backlog completion, and leverage rule-based or DeepSeek-powered recommendations.221MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Planka kanban boards, including creating, updating, and organizing tasks, lists, and cards via MCP.22 npm60MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with Planka, a real-time Kanban board application, for managing projects, boards, lists, cards, and more.1044 npm5MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage a persistent Scrumban board through natural language, including capturing, moving, and completing tasks, with leasing, progress reporting, and human-in-the-loop decision handling.14 npmMIT
TDQS
A3.9/5.0
Scored across 33 tools
Disambiguation4/5
Tools generally map to distinct resource/action pairs (boards, projects, lists, tasks, labels, people), and the descriptions explicitly differentiate close pairs like move_task vs update_status and create_project vs copy_project_structure. A few genuine overlaps remain—update_task_details and set_task_labels both change labels, and attach_link vs add_result both attach output—but they are unlikely to cause frequent misselection.
Naming Consistency4/5
Almost every tool follows a verb_noun snake_case pattern (list_boards, create_task, update_status, assign_people), which makes the set predictable. Minor deviations like whoami and admin_manage_person, plus compound names like find_informal_assignments, keep it from being perfectly uniform.
Tool Count2/5
33 tools is beyond the 25-tool threshold and feels heavy for a single server, even for a rich project-management domain. Several tools bundle multiple operations (admin_manage_person) and label-related behavior is split across three tools, so the surface could be consolidated.
Completeness4/5
The lifecycle is well covered: boards/projects/lists can be created and updated, tasks have claim/status/assignment/result/comment flows, and search/audit tools expose informal assignments. Missing destructive or cleanup operations (delete/archive task, delete board/project, remove attachment/comment) are notable but mostly work-aroundable.
Maintenance
ActivityNo data
ResponsivenessNo issues