A
licenseA
qualityB
maintenanceEnables to interact with Bitbucket Server repositories, pull requests, and code reviews, including file browsing, PR management, and review actions through natural language.
59
8 npm
Apache 2.0
atlassian-mcp
by stubbedev
Related Servers
Alternatives to atlassian-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables interaction with self-hosted Jira instances via Personal Access Token, supporting issue management and project operations through natural language.76 npmApache 2.0
- AlicenseBqualityBmaintenanceEnables AI assistants to interact with Bitbucket Cloud and self-hosted instances for pull request reviews, code search, repository operations, and managing PR comments and approvals.19GPL 3.0
- AlicenseAqualityCmaintenanceEnables natural-language interaction with self-hosted Jira through the Jira REST API, supporting PAT or browser-cookie/SSO authentication. It allows viewing and managing issues, projects, comments, assignments, and statuses, as well as JQL search and issue creation/deletion.121 npmMIT
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to Bitbucket Server/Data Center for reviewing pull requests, managing repositories, searching users, and more.149 npm4MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with Atlassian Cloud (Jira, Confluence, Bitbucket) through natural language, providing CRUD operations for issues, pages, pull requests, and more.868 npmMIT
TDQS
A3.9/5.0
Scored across 10 tools
Disambiguation2/5
git_get_context and get_dev_context both claim to be the master entry point for coding/review tasks and return heavily overlapping git+Jira status information, making it unclear which one to call. jira_comment also duplicates the comment capability already bundled inside jira_mutate, further blurring tool boundaries.
Naming Consistency3/5
Most Jira tools follow a readable jira_<verb_or_noun> pattern and Git tools use git_get_*, but get_dev_context and start_work break the prefix convention, and jira_mutate uses a vague verb instead of a concrete resource-action name. The naming is still mostly predictable despite these deviations.
Tool Count4/5
10 tools is a reasonable size for a combined Jira/Git workflow and covers the major operations without feeling bloated. The count is slightly higher than needed because of overlapping entry-point tools and duplicated comment functionality, but it is still well within an appropriate range.
Completeness4/5
The set covers core Jira lifecycle operations, attachment retrieval, version management, git context, and diff inspection. Notable gaps include PR creation/merging despite those actions being hinted at in descriptions, and no explicit issue deletion, but most workflows can be completed with the existing tools.
Maintenance
ActivityActive
ResponsivenessResponsive