scrumdo-mcp
OfficialRelated Servers
Alternatives to scrumdo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Planka kanban boards, including creating, updating, and organizing tasks, lists, and cards via MCP.8 npm59MIT

@letretro/mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI coding tools to access LetRetro retrospectives, boards, cards, and team data through MCP.16 npm1MIT- 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

GitScrum MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage projects, tasks, sprints, time tracking, and more through GitScrum.56 npm5MIT- AlicenseNot gradedqualityBmaintenanceEnables users to interact with Planka (a Trello-like kanban tool) through natural language, using their own Planka access tokens for authentication and permissions. Supports remote hosting via HTTP, allowing multi-user MCP access to boards, lists, cards, and more.8 npmMIT
- FlicenseAqualityDmaintenanceIntegrates BusinessMap (formerly Kanbanize) project management capabilities with MCP-compatible applications, enabling board management, card operations, user management, and search.9-
TDQS
Scored across 45 tools
Each tool has a clearly distinct purpose, covering cards, tasks, comments, labels, blockers, time tracking, activity logging, webhooks, and search. Only minor aliasing like find_card=get_card, which does not cause confusion.
Most tools follow a consistent verb_noun pattern (create_card, list_tasks, etc.). However, there is some variation in prefix verbs (get vs list vs find vs search) and a few tools like log_activity and log_time use a different structure, preventing a perfect score.
With 45 tools, the set is quite large but each tool serves a specific function within a comprehensive project management domain. It borders on excessive but remains justified given the breadth of features supported.
The tool surface covers most CRUD operations for core entities but misses lifecycle operations for iterations, epics, and boards (e.g., no create/delete). Card deletion is only via archiving, which is a notable gap.