F
licenseNot graded
qualityB
maintenanceEnables AI agents to manage Jira and Confluence directly, including issue tracking, sprint management, and knowledge base operations through natural language.
-
jira-mcp
by Choing-dev
Related Servers
Alternatives to jira-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with Jira and Confluence on Atlassian Cloud, supporting issue search, creation, updates, transitions, project listing, content search, page management, and comments.132 npm1MIT
- FlicenseAqualityCmaintenanceEnables AI agents to manage Jira Cloud issues through natural language, including searching, creating, updating, commenting, assigning, and transitioning issues.10-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage Jira issues and Confluence pages, including creating, updating, searching, commenting, and transitioning work items through natural language.MIT
- 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
- 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
TDQS
A3.7/5.0
Scored across 10 tools
Disambiguation5/5
Each tool targets a distinct action or resource: search, get, create, update, transition, comment, projects, and user info are clearly separated. get_transitions and transition_issue are complementary rather than overlapping, with descriptions explicitly guiding the intended workflow.
Naming Consistency4/5
Most tools follow a clear verb_noun snake_case pattern like get_issue, create_issue, and list_projects. jql_search is a minor outlier (should be search_jql), and confluence_create_page mixes a namespace prefix with the otherwise consistent pattern.
Tool Count5/5
Ten tools is well-scoped for a Jira integration, covering search, issue lifecycle, transitions, comments, projects, and user lookup without unnecessary bloat. The Confluence page creation tool is slightly out of place, but the overall count remains appropriate and manageable.
Completeness4/5
The core Jira workflow is well covered: search, create, read, update, transition, comment, project listing, and user identity are all present. Minor gaps like deleting issues, managing attachments/links, and Confluence read/update operations are acceptable for a typical Jira automation surface.
Maintenance
ActivityInactive
ResponsivenessNo issues