mcp-atlassian
Related Servers
Alternatives to mcp-atlassian
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI assistants to interact with Atlassian Jira and Confluence across Cloud and Server/Data Center environments. It supports tasks like searching and summarizing documentation, managing Jira issues, and creating content through natural language.MIT
- AlicenseBqualityBmaintenanceMCP server for Atlassian products (Confluence and Jira) that enables AI assistants to search, create, update, and manage issues and pages through natural language.98MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Atlassian Confluence and Jira, enabling AI assistants to search, create, and update issues and pages via natural language.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that integrates with Jira and Confluence to enable AI-powered issue management, content search, and document creation. It supports both Cloud and on-premise deployments, allowing users to automate workspace tasks through natural language.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Atlassian products (Confluence, Jira, Bitbucket, and Xray for Jira) supporting Cloud and Server/Data Center deployments.MIT
- AlicenseNot gradedqualityAmaintenanceMCP servers for self-hosted Atlassian Data Center (Jira, Confluence, Bitbucket) enabling AI assistants to search, manage, and interact with issues, pages, and pull requests.3MIT
TDQS
Scored across 71 tools
Most tools have distinct resource+action targets, but a few overlapping ones like jira_download_attachments vs jira_save_attachment_to_disk could cause confusion. Search/issue-listing tools (jira_search, jira_get_project_issues, jira_get_board_issues) also share similar behavior but differ in scope.
All tools follow a product-prefix (jira_, confluence_, bitbucket_) with verb_noun structure, which is consistent. However, there are deviations like 'jira_jira_upload_attachment' (duplicated prefix), 'bitbucket_pull_request_activities' (missing verb), and mixed verb choices (get vs list) that prevent a perfect score.
With 71 tools, the server is extremely large, exceeding even the 25+ threshold. While it covers three separate products (Jira, Confluence, Bitbucket), the sheer number makes it heavy and harder to navigate, and many tools are narrowly scoped.
Core workflows for Jira (issues, sprints, projects, attachments), Confluence (pages, comments, labels), and Bitbucket (repos, PRs, commits, file access) are well-covered. Obvious gaps like merging PRs, deleting branches/comments, or updating PRs are missing but can be worked around via other means.