A
licenseA
qualityNot graded
maintenanceEnables AI assistants to interact with Atlassian Jira Cloud, allowing users to manage projects, issues, comments, and workflows through natural language commands.
6
73 npm
3
-
jira-mcp-server
by BillNobill
Related Servers
Alternatives to jira-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Jira Cloud through the REST API, supporting project management, issue operations (create, read, update, delete), JQL search, task assignments, and status transitions.-
- AlicenseBqualityDmaintenanceEnables AI agents to manage Jira Cloud projects with full CRUD operations, bulk actions, sprint and release management, and issue linking using natural language.27MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to manage Jira and Confluence directly, including issue tracking, sprint management, and knowledge base operations through natural language.-
- FlicenseAqualityCmaintenanceEnables AI agents to manage Jira Cloud issues through natural language, including searching, creating, updating, commenting, assigning, and transitioning issues.10-
- FlicenseNot gradedqualityDmaintenanceEnables AI systems to interact with JIRA through natural language, allowing users to retrieve issue details, create new tickets, search using JQL, and access project information.3-
TDQS
B3.2/5.0
Scored across 36 tools
Disambiguation5/5
Each tool targets a distinct resource and action, with clear separation between issues, comments, worklogs, sprints, versions, attachments, and user operations. Even similar-sounding tools like update_sprint and update_sprint_state are clearly differentiated by descriptions focusing on details vs state.
Naming Consistency4/5
Most tools follow a verb_noun snake_case pattern, but there are minor singular/plural inconsistencies such as create_issue vs delete_issues and update_sprint vs delete_sprints. Bulk operations are consistently prefixed with bulk_, but delete operations also support bulk without a prefix.
Tool Count2/5
With 36 tools, the server far exceeds the typical 3-15 tool range and crosses the 25-tool threshold for a well-scoped set. While Jira is complex, the breadth here feels heavy and could overwhelm agents.
Completeness4/5
The tool set provides strong CRUD coverage for issues, comments, worklogs, sprints, versions, and attachments, plus search, transitions, and linking. Minor gaps exist, such as no direct getters for comments or worklogs and no tool to list issue link types, but core workflows remain functional.
Maintenance
ActivitySlowing
ResponsivenessNo issues