A
licenseB
qualityC
maintenanceEnables 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.
35
MIT
MCP Atlassian Server
by dunz
Related Servers
Alternatives to MCP Atlassian Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Atlassian Confluence and Jira for searching, updating, and managing content and issues.MIT
- AlicenseBqualityAmaintenanceEnables AI assistants to interact with Atlassian Cloud APIs for Confluence and Jira, supporting document management, search, issue tracking, and sprint operations through natural language.402MIT
- 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
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Atlassian products (Confluence and Jira) through natural language, supporting both Cloud and Server/Data Center deployments. Allows searching, creating, and managing content across Jira issues and Confluence pages with flexible authentication options.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage Jira issues and Confluence pages, including creating, updating, searching, commenting, and transitioning work items through natural language.MIT
TDQS
A3.6/5.0
Scored across 40 tools
Disambiguation4/5
Most tools have clearly distinct purposes (Confluence vs Jira, different actions). However, a few pairs like 'get_confluence_user' vs 'find_confluence_users' and 'list_issues_by_user_role' vs 'search_issues_by_user_involvement' could cause minor confusion, but descriptions help disambiguate.
Naming Consistency5/5
Consistent verb_noun pattern with snake_case throughout. Prefixes like add_, create_, get_, list_, search_ are uniform. Minor variation between 'get' and 'read' for different resource types but this aligns with standard conventions.
Tool Count3/5
40 tools is high, covering both Confluence and Jira extensively. While each tool serves a distinct purpose, the count feels heavy for a single server, bordering on overwhelming. A more focused subset might improve usability.
Completeness3/5
Covers many operations (create, read, search, list, add comments/labels/attachments) but lacks update and delete for Jira issues, and no issue transitions. These are notable gaps that may hinder agent workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues