A
licenseNot graded
qualityC
maintenanceProvides Jira and Confluence integration for AI assistants, enabling natural language management of issues, projects, sprints, pages, comments, attachments, and more with 72 tools.
MIT
Jira & Confluence MCP Server
by halim-23
Related Servers
Alternatives to Jira & Confluence MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage Jira issues and Confluence pages, including creating, updating, searching, commenting, and transitioning work items through natural language.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to manage Jira and Confluence directly, including issue tracking, sprint management, and knowledge base operations through natural language.-
- AlicenseAqualityDmaintenanceEnables AI agents to interact with Jira Cloud and Confluence through natural language, performing JQL searches, issue management, and Confluence page creation.103 npm1MIT
- AlicenseCqualityDmaintenanceEnables AI assistants to manage Jira Cloud projects, issues, sprints, and more through a curated set of 62 tools covering the full lifecycle of stories, epics, bugs, and sprints.62GPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Atlassian Confluence and Jira for searching, updating, and managing content and issues.MIT
TDQS
B3.4/5.0
Scored across 53 tools
Disambiguation5/5
Each tool is clearly prefixed with 'confluence_' or 'jira_', and within each domain, they target distinct actions and resources (e.g., create vs. get, page vs. space vs. issue, comments vs. labels). There is no ambiguity between tools.
Naming Consistency5/5
All tools follow a consistent pattern: product prefix + verb_noun (e.g., jira_create_issue, confluence_get_page). The naming conventions are uniform and predictable across the entire set.
Tool Count4/5
With 53 tools covering two major platforms, the count is high but justifiable. Each tool serves a specific purpose, and the scope is broad. However, some consolidation (e.g., a single get_issues with optional filters) could reduce redundancy without losing functionality.
Completeness4/5
The tool set covers most CRUD operations, search, comments, labels, sprints, boards, and workflows for both Jira and Confluence. Notable omissions include file attachments (e.g., adding attachments to issues or pages) and creating Confluence blog posts, but core workflows are well-supported.
Maintenance
ActivityInactive
ResponsivenessNo issues