Task360 MCP
Related Servers
Alternatives to Task360 MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI coding assistants to search, create, update, and manage Jira issues, users, and projects via natural language, using the Jira REST API and MCP stdio transport.496 npmMIT
- AlicenseBqualityDmaintenanceProvides tools for AI assistants to interact with JIRA APIs, enabling them to read, create, update, and manage JIRA issues through standardized MCP tools.610 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables local MCP-based interaction with Jira Cloud, offering tools for issues, comments, transitions, worklogs, attachments, and user lookups while addressing gaps like attachment downloads, mention notifications, and multi-step status transitions.496 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables natural language interaction with JIRA through MCP, providing 35 tools for issues, comments, transitions, projects, boards, sprints, epics, links, worklogs, versions, attachments, users, and fields.MIT
- FlicenseNot gradedqualityDmaintenanceEnables natural language interaction with Jira Cloud tickets, including listing, searching, creating, and updating issues through a set of MCP tools.-
- FlicenseBqualityBmaintenanceMCP server that connects AI assistants to your Jira site, supporting PAT or SSO authentication for search, read, create, update, and delete operations on issues.17110 npm-
TDQS
Scored across 11 tools
Most tools have clearly distinct purposes tied to specific resources and actions. The only mild overlap is between get_ticket, get_my_tickets, and search_tickets, but descriptions clarify that one fetches by key while the others filter by assignee/query. get_transitions vs transition_ticket are also well differentiated (read vs execute).
The set follows a mostly predictable verb_noun pattern (get_ticket, update_ticket, delete_ticket, create_ticket, search_tickets). Minor deviations like transition_ticket (noun-as-verb) and the mix of get_/add_ verbs are readable but slightly inconsistent.
11 tools is well-scoped for a ticket management server, with each tool earning its place across read, write, search, workflow, and comment operations. No redundant or filler tools.
Ticket lifecycle is well covered with create, get, update, delete, plus workflow transitions and comments. Minor gaps exist on the comment side (no edit/delete comment) and workspace-level operations, but agents can work around these.