F
licenseNot graded
qualityD
maintenanceEnables 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
-
Jira MCP Server
Related Servers
Alternatives to Jira MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search, view, create, and update JIRA issues using natural language commands and JQL queries.60 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Jira Cloud issues, supporting create, read, update, delete, search, and transition operations via natural language.9 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.66 npm3MIT
- AlicenseNot gradedqualityBmaintenanceConnects AI assistants to Jira, enabling retrieval, search, creation, and update of issues with schema validation.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Jira Cloud by managing issues, comments, custom fields, and sprint tasks through a standardized interface. Supports issue creation, updates, team activity tracking, and progress reporting.1160 npmApache 2.0
TDQS
B3.4/5.0
Scored across 5 tools
Disambiguation3/5
Tools are mostly distinct but there is functional overlap between 'get_jira_issue_details' and 'list_jira_issues', both accepting issue keys and returning issue information (though with different detail levels). Additionally, 'get_jira_issues_by_sprint' could be considered a filtered variant of 'list_jira_issues', causing potential confusion for an agent.
Naming Consistency4/5
All tool names follow snake_case and use a verb-noun pattern. However, there is a mix of 'get_' and 'list_' prefixes (e.g., 'list_jira_issues' vs. 'get_jira_issue_details'), which is a minor inconsistency but not chaotic.
Tool Count5/5
With 5 tools, the server is well-scoped for a read-only Jira query interface. The tools cover essential retrieval needs (issue details, links, sprint issues, project summary, and filtered list) without being excessive or overly sparse.
Completeness4/5
The tool surface covers the main read operations for Jira issues from Snowflake, but is limited to querying. Missing operations like creating, updating, or transitioning issues are not expected given the read-only nature, so there are only minor gaps such as lacking a direct single-issue getter (though details and list can serve that role).
Maintenance
ActivityInactive
ResponsivenessNo issues