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
custom-atlassian-mcp
Related Servers
Alternatives to custom-atlassian-mcp
No user-submitted related servers found.
Related Servers
- 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 gradedqualityAmaintenanceMCP server for interacting with Jira Cloud instances. Enables issue management, JQL queries, project and sprint management, and batch operations via natural language interfaces.195 npm4MIT
- AlicenseNot gradedqualityCmaintenanceSelf-hosted MCP server for Jira Cloud that mirrors the Atlassian Rovo MCP Server, enabling Jira issue management, JQL search, and workflow transitions via natural language.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for integrating with Jira Server instances, enabling natural language interactions to create, update, search, and manage issues and comments.60 npm1MIT
- AlicenseAqualityAmaintenanceMCP server for Jira Cloud enabling issue tracking, comments, transitions, and attachments management through natural language.5MIT
TDQS
A4/5.0
Scored across 12 tools
Disambiguation5/5
Each tool targets a distinct resource and action: Jira issues vs sprints vs comments, Confluence pages vs search. No two tools have overlapping purposes, and descriptions clarify even similar verbs like update_issue vs transition_issue.
Naming Consistency4/5
All tools follow a consistent snake_case pattern with a domain prefix (jira_/confluence_) and verb. Minor deviations: search omits an object (e.g., jira_search vs jira_get_issue) and add_issues uses plural, but the pattern is still predictable.
Tool Count5/5
12 tools is well-scoped for an Atlassian server covering Jira and Confluence. Each tool earns its place, covering search, read, create, update, and specialized actions without bloat.
Completeness4/5
Core CRUD and lifecycle operations are covered for both Jira (search, get, create, update, transition, comment, sprint management) and Confluence (search, get, create, update). Missing delete operations and project/space listing are minor gaps that agents can work around.
Maintenance
ActivityStale
ResponsivenessNo issues