kanopy
Related Servers
Alternatives to kanopy
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceSelf-hosted kanban board that dispatches AI agent fleets against tickets. The embedded Streamable HTTP /mcp endpoint exposes 7 tools to list projects, read boards and tickets, and create, move and comment tickets from any MCP client.31AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceA local kanban board and docs tool that AI agents can drive over MCP. It enables project management without accounts or API keys.MIT

AgentTaskerofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to create, query, update, claim, hand off, and complete tasks on a local SQLite-backed, project-namespaced kanban board through stdio MCP tools, including filtering for ready/blocked/stale work and exchanging task attachments. It also lets agents list projects and manage statuses, ownership, and evidence without any server or accounts.MIT- FlicenseNot gradedqualityDmaintenanceA local-first Kanban system with MCP tools for AI agents to manage tickets, features, and tasks, paired with a React UI for human users.-
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to work from the same self-hosted kanban board as their user, picking up tasks, moving cards between statuses, and commenting on progress. The board runs locally with no account or server, and agents can be pointed at projects by their git remote.1,261AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceAn AI-native kanban board MCP server where agents pull tasks via the Model Context Protocol. It provides tools for task discovery, claiming, progress updates, and review workflows.5MIT
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes: list_projects vs list_tasks, get_task vs list_tasks, and save_task vs save_project are all separable by resource and action. The main fuzziness is that project creation happens inside save_task (save_project only updates), and delete/labels are multi-resource or multi-action tools whose scope must be read carefully.
Half the set follows verb_noun (list_projects, save_project, get_task, list_tasks, save_task), but the rest are bare nouns or verbs (comment, link, labels, inbox, delete), and several tools hide multiple actions behind a single name. It remains readable, but there is no single predictable pattern an agent can extrapolate from.
Ten tools is well within the ideal range and each one maps to a real part of a project/task workflow (projects, tasks, comments, relations, labels, notifications, trash). No tool feels redundant or padded.
CRUD is largely covered for tasks (save_task, get_task, list_tasks, delete/restore) and projects (list/save/delete, creation via save_task), plus links, labels, comments, and inbox. Gaps remain: comments can be added but not edited or deleted, and get_task can read attachment text but there is no tool to upload or attach a file.