GitHub Kanban MCP Server
Related Servers
Alternatives to GitHub Kanban MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides AI assistants with structured access to kanban board functionality for managing tasks, columns, labels, and sprints.8 npm2MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables LLM agents to manage GitHub repositories, issues, pull requests, branches, files, and releases through a standardized interface.245 npm8Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to perform GitHub operations including repository management, file operations, issue tracking, and pull request creation.2-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact with GitHub repositories, issues, and pull requests.13 npmMIT
- FlicenseAqualityDmaintenanceA Model Context Protocol server that enables management of GitLab Kanban boards through tools for listing, creating, updating, and deleting tasks, as well as adding comments.53-
- AlicenseBqualityFmaintenanceA Model Context Protocol server that enables LLMs to interact with Plane.so, allowing them to manage projects and issues through Plane's API for streamlined project management workflows.640MIT
TDQS
Scored across 4 tools
Each tool targets a distinct operation: listing, creating, updating, or commenting on issues. No two tools overlap in purpose, so an agent can clearly distinguish them.
All tool names follow a consistent snake_case verb_noun pattern (list_issues, create_issue, update_issue, add_comment). The verbs are clear and predictable.
With 4 tools, the server is tightly scoped to core Kanban board operations. Every tool serves a necessary function without redundancy or bloat.
The basic lifecycle of issues is covered (list, create, update, comment). Missing operations like deleting or archiving issues are a minor gap since GitHub issues are typically closed rather than deleted, but board-specific transitions are not explicitly exposed.