ya-planka-mcp
Related Servers
Alternatives to ya-planka-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact directly with Planka Kanban boards, allowing automated management of projects, tasks, and workflows through conversational interfaces.814 npm1MIT
- 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
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that exposes Kanboard API functionality to Large Language Models (LLMs), enabling AI assistants to interact with Kanboard project management system.2MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that connects Hermes to Planka Kanban, enabling natural language management of projects, boards, lists, cards, and users through the Planka REST API.-
- 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.6 npmMIT
TDQS
Scored across 38 tools
Most tools have clearly distinct purposes, such as creating, updating, deleting, or retrieving specific entities. However, slight overlap exists between 'planka_find_and_get_card' and 'planka_get_card', and 'planka_get_labels' may be redundant with workspace data, but descriptions clarify intent.
The vast majority follow a consistent 'planka_verb_noun' pattern (e.g., planka_create_card, planka_delete_label). A few outliers like 'planka_board_status' and 'planka_card_ready_check' break the pattern, and 'planka_next_card' uses an adjective as verb, but overall naming is predictable.
38 tools is on the higher end but appropriate for a full-featured project management server covering boards, lists, cards, labels, custom fields, tasks, comments, and members. Each tool serves a specific action, and while a few could be merged, the count is reasonable for the domain.
The tool set covers most core operations (CRUD for cards, labels, custom fields, tasks, comments), but lacks board update/delete, list delete, and comment delete. The presence of specialized tools like 'planka_board_status' and 'planka_card_ready_check' indicates attention to workflows, yet gaps remain.