A
licenseB
qualityC
maintenanceMCP server for Jira and Confluence integration with 32 tools for managing tickets, sprints, boards, worklogs, and Confluence pages.
37
32 npm
1
GPL 2.0
mcp-atlassian-extended
by vish288
Related Servers
Alternatives to mcp-atlassian-extended
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for Atlassian Confluence and Jira Cloud with 51 tools to manage pages, issues, sprints, boards, and backlogs.729 npm7MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Atlassian Confluence and Jira, supporting both Cloud and Server/Data Center deployments with tools for searching, creating, and updating issues and pages.MIT
- AlicenseAqualityDmaintenanceAn MCP server that provides tools to interact with JIRA for sprint management, issue tracking, and attachment handling.2329 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for interacting with Jira Cloud, providing tools for issues, search, agile boards, comments, links, attachments, and webhook notifications.7 npm2MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for Jira that enables comprehensive issue management, sprint operations, comments, attachments, and batch processing with localization and flexible date support.625 npm2MIT
TDQS
B3/5.0
Scored across 26 tools
Disambiguation3/5
Most Jira tools target distinct resources, but there are confusing clusters: confluence_who_is_out, confluence_get_time_off, and confluence_get_person_time_off all deal with time-off, while jira_create_issue overlaps with jira_create_epic. jira_get_board and jira_board_config also have fuzzy boundaries.
Naming Consistency3/5
Tool names consistently use jira_ and confluence_ prefixes, but verb style is mixed: list, get, search, and create are used inconsistently. Several names omit a verb entirely, such as jira_backlog, jira_board_config, and confluence_who_is_out, making the pattern readable but not uniform.
Tool Count2/5
At 26 tools, the set exceeds the 25-tool threshold and includes many niche calendar/time-off helpers alongside Jira operations, making it feel overloaded. The broad Atlassian scope justifies some size, but several peripheral tools overlap with others and dilute the focus.
Completeness2/5
Core Jira workflows are incomplete: there is no get/search issue, no issue transitions, no comments, and no delete/archive for issues. Confluence coverage is almost entirely limited to calendar/time-off, so agents cannot perform basic page or content operations.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive