F
licenseA
qualityF
maintenanceEnables interaction with Jira and Confluence APIs to search, create, and manage issues, pages, comments, and attachments across both Atlassian platforms.
7
-
@ama-work/mcp-atlassian
Related Servers
Alternatives to @ama-work/mcp-atlassian
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Atlassian Confluence and Jira through natural language, allowing users to search, create, update, and transition issues and pages.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with Jira and Confluence on Atlassian Cloud, supporting issue search, creation, updates, transitions, project listing, content search, page management, and comments.103 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Atlassian Confluence and Jira for searching, updating, and managing content and issues.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search, create, update, and transition Jira issues and Confluence pages, add comments, and manage Atlassian content across Cloud and Server/Data Center deployments.MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to search and manage Confluence pages and Jira issues, including creating, updating, transitioning, and commenting, across Atlassian Cloud and Server/Data Center deployments.35MIT
TDQS
A3.7/5.0
Scored across 14 tools
Disambiguation5/5
Every tool is clearly scoped by domain prefix (jira_, confluence_, atlassian_) and a distinct action, so there is no real overlap. Similar tools like jira_add_comment and confluence_add_comment are separated by their domain prefix, and analogous tools like jira_get_projects vs confluence_get_spaces target different resources.
Naming Consistency4/5
Tool names follow a predictable domain_verb_noun pattern in snake_case, such as jira_search_issues and confluence_create_page. The only minor deviation is atlassian_whoami, which uses a command-style noun rather than a verb_noun structure, but it remains readable and clearly namespaced.
Tool Count5/5
14 tools is well within the ideal range and appropriately covers two product areas (Jira and Confluence) plus an identity check. Each tool serves a distinct purpose and none feel redundant or excessive for the server's broad Atlassian scope.
Completeness4/5
The tool surface covers core Jira and Confluence workflows: search, create, read, update, transition/comment, plus project/space discovery and identity. Minor gaps exist such as no delete operations, no listing of available Jira transitions, and no page comment retrieval, but agents can still accomplish most common tasks without dead ends.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive