@kanbio/mcp
Related Servers
Alternatives to @kanbio/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants such as Claude Desktop and Cursor to inspect backlogs, plan sprints, and manage projects through eight tools for listing, searching, creating, updating, and deleting tickets plus project summaries. Changes made by agents are reflected in the desktop board in real time over a local stdio connection.1MIT
- FlicenseBqualityDmaintenanceStdio-based MCP server exposing Jira tools for searching, creating, getting, commenting on, assigning, and transitioning issues, as well as listing projects, with authentication via token or basic auth.7-
- AlicenseAqualityCmaintenanceMCP server enabling AI assistants to interact with Jira, scoped to a single project. Supports stdio and HTTP transports for issue management operations.128 npmISC
- AlicenseAqualityBmaintenanceEnables agents to work with Jira Server, Data Center, and Cloud instances over stdio, including searching issues with JQL, reading boards/backlogs/sprints, creating and updating issues, moving them through workflows by status name, and logging work, comments, links, and attachments. The server projects issues into compact cards and auto-detects deployment type and authentication so no board IDs, project keys, or custom field IDs need to be hardcoded.25331 npmMIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to interact with Jira via CLI/TUI, supporting issue browsing, creation, comments, status changes, and custom fields.3Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables seamless Jira issue and sprint management directly from the terminal or IDE without context switching. Supports full issue lifecycle operations including creation, updates, and search, plus sprint planning, commenting, and project analytics through natural language commands.-
TDQS
Scored across 12 tools
Each tool targets a distinct action-resource pair: status, assignee, and sprint moves are deliberately split into change_status, assign_ticket, and move_to_sprint, and update_ticket explicitly excludes them. The only slight overlap is my_tickets vs search_tickets, but the descriptions make the boundary clear (assigned-to-me shortcut vs filtered search).
The set is overwhelmingly consistent verb_noun (list_projects, create_ticket, update_ticket, change_status, assign_ticket, move_to_sprint, search_tickets, get_ticket). The single deviation is my_tickets, a noun-only name with no verb, which breaks the pattern but is still readable.
Twelve tools is well within the ideal range and each one maps to a concrete workflow step (discovery, read, search, create, edit, status, assign, sprint, comment, members). No tool appears redundant or filler.
Ticket lifecycle is well covered: create, read, search, edit, status transitions with documented workflow, assignment, sprint placement, and commenting via get_ticket. Minor gaps exist (no ticket delete/archive, no sprint creation despite list_sprints, no comment editing), but core agent workflows are not blocked.