A
licenseNot graded
qualityF
maintenanceEnables AI assistants to manage Jira projects, issues, sprints, and boards via natural language.
30 npm
MIT
jira-mcp
by thammarongg
Related Servers
Alternatives to jira-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search, create, update, and transition Jira issues and Confluence pages, add comments, and manage Atlassian content across Cloud and Server/Data Center deployments.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage Jira issues and Confluence pages, including creating, updating, searching, commenting, and transitioning work items through natural language.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search, view, create, and update JIRA issues using natural language commands and JQL queries.30 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.15 npmMIT
- AlicenseBqualityCmaintenanceEnables AI assistants to search and manage Confluence pages and Jira issues, including creating, updating, transitioning, and commenting, across Atlassian Cloud and Server/Data Center deployments.35MIT
TDQS
B3.3/5.0
Scored across 43 tools
Disambiguation4/5
Most tools target a distinct resource and action, and descriptions clarify likely variants like get_sprint, get_sprint_issues, and get_sprint_view. A few close pairs exist—get_issue_types vs get_project_issue_types and update_issue vs move_issue_to_epic—but the resource scopes and descriptions make misselection unlikely.
Naming Consistency3/5
The set mostly follows verb_noun, but it mixes get_ and list_ for collections, uses create_ for most resources but add_ for comments and worklogs, and uses search_issues versus find_users. jira_api also breaks the pattern, making the naming readable but not consistently structured.
Tool Count2/5
43 tools is well beyond the 25+ threshold, and the surface includes many fine-grained getters plus a catch-all jira_api tool. While Jira is a broad domain, the large count makes agent tool selection heavier than necessary, and some variants could reasonably be consolidated.
Completeness4/5
Core Jira workflows—issues, sprints, epics, projects, comments, worklogs, and users—are well covered with appropriate create/read/update/delete operations where relevant. Minor gaps exist, such as no update_comment, no delete_sprint, or no direct add-issue-to-sprint tool, but jira_api and update_issue provide usable workarounds.
Maintenance
ActivityMaintained
ResponsivenessNo issues