A
licenseA
qualityA
maintenanceEnables interaction with Atlassian Jira and Confluence via their REST API, providing tools for searching, creating, updating, commenting, and retrieving issues, pages, projects, and spaces.
14
10 npm
MIT
Jira & Confluence MCP Server
Related Servers
Alternatives to Jira & Confluence MCP Server
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 gradedqualityDmaintenanceEnables AI assistants to interact with Atlassian Confluence and Jira for searching, updating, and managing content and issues.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.88 npm1MIT
- 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.5/5.0
Scored across 7 tools
Disambiguation5/5
Every tool has a clearly distinct purpose with no ambiguity. Each targets a specific Jira action (e.g., create, get, update, search, transition, add comment, list projects) with no overlap in functionality. The descriptions make it easy to differentiate between tools like jira_update_issue and jira_transition_issue.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with a 'jira_' prefix (e.g., jira_create_issue, jira_get_issue). The naming is predictable and readable throughout, using snake_case uniformly without any deviations or mixed conventions.
Tool Count5/5
The 7 tools are well-scoped for a Jira-focused server, covering core operations without being excessive. Each tool earns its place by addressing essential Jira workflows (e.g., issue lifecycle, project management, searching). This count is appropriate for the domain, avoiding both thinness and bloat.
Completeness4/5
The tool set provides strong coverage for Jira operations, including CRUD for issues (create, get, update), search, transitions, comments, and project listing. A minor gap is the lack of tools for Confluence (implied by the server name), but for Jira alone, it's nearly complete with only small omissions like deleting issues or managing users.
Maintenance
ActivityInactive
ResponsivenessNo issues