A
licenseB
qualityC
maintenanceMCP server for Jira and Confluence integration with 32 tools for managing tickets, sprints, boards, worklogs, and Confluence pages.
37
5 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.706 npm8MIT
- 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.236 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for interacting with Jira Cloud, providing tools for issues, search, agile boards, comments, links, attachments, and webhook notifications.5 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.301 npm2MIT
TDQS
B3.2/5.0
Scored across 22 tools
Disambiguation4/5
Most tools target clearly distinct resources: attachments (list/download/upload/delete), versions (create/update/list), boards/sprints, and Confluence calendars are well separated. Minor potential confusion exists around board-related tools (jira_get_board, jira_board_config, jira_backlog) and sprint tools, but descriptions disambiguate them adequately.
Naming Consistency4/5
Names follow a consistent 'product_verb_noun' snake_case convention with jira_/confluence_ prefixes throughout, which is highly predictable. A few entries are noun-only (jira_board_config, jira_backlog, confluence_sprint_capacity) rather than verb-led, a minor deviation from the rest.
Tool Count4/5
22 tools is on the heavier side but justified by an 'extended' server spanning two products (Jira and Confluence) with agile, attachment, version, and time-off domains. Each tool maps to a distinct operation, so little feels redundant despite the count.
Completeness3/5
Coverage is uneven: attachments have full lifecycle and versions have create/update/list, but there is no issue search/get, no delete-issue, no comment tools, and no delete-version. An agent can create and update issues but lacks a general way to retrieve or search them beyond the backlog endpoint.
Maintenance
ActivityActive
ResponsivenessUnresponsive