A
licenseNot graded
qualityB
maintenanceMCP server for Atlassian Confluence and Jira, enabling AI assistants to search, create, and update issues and pages via natural language.
MIT
MCP Atlassian
by hieptran87
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
- 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
- AlicenseBqualityAmaintenanceAn MCP server for integrating with Atlassian products including Confluence, Jira, Bitbucket, and Xray for Jira, enabling AI-powered operations like searching, creating, and updating issues, pages, and test results.7227MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for Atlassian Jira that enables AI assistants to manage issues, sprints, comments, and worklogs through 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
TDQS
B3.4/5.0
Scored across 98 tools
Disambiguation3/5
Most tools follow a clear resource+action pattern, but there are genuine overlaps: jira_update_issue can transition, comment, and log work alongside dedicated jira_transition_issue, jira_add_comment, and jira_add_worklog tools; jira_get_issue_dates and jira_get_issue_sla both analyze status/time; and multiple issue-listing variants (project, board, sprint, queue, JQL) require careful selection. The descriptions do a good job of clarifying scope, so the ambiguity is manageable but not eliminated.
Naming Consistency5/5
All tools consistently use snake_case with jira_/confluence_ prefixes and a clear verb_noun structure: get_, create_, update_, delete_, add_, remove_, search_. Batch variants follow the same pattern (batch_create, batch_get, upload_attachments), making the naming highly predictable across 98 tools.
Tool Count1/5
98 tools is far beyond even the 50+ extreme-mismatch threshold. While the server legitimately spans both Jira and Confluence with many subdomains, the sheer surface area creates a heavy navigation burden for agents and could benefit from consolidation or modular sub-servers.
Completeness4/5
The toolset provides remarkably comprehensive coverage: Jira issues, transitions, comments, worklogs, watchers, links, attachments, sprints, versions, projects, fields, forms, SLA/dev info, and Confluence pages, comments, labels, restrictions, permissions, attachments, templates, and history/diff. Minor gaps such as no Jira delete-comment, no Confluence delete-comment, and no remove-remote-link keep it from a 5, but agents can generally work around these.
Maintenance
ActivitySlowing
ResponsivenessNo issues