A
licenseNot graded
qualityC
maintenanceEnables AI agents to manage self-hosted Atlassian Jira Server/Data Center issues and Bitbucket Server/Data Center repositories, pull requests, branches, commits, and files through MCP tools.
6 npm
4
MIT
Jira + Confluence MCP
by itsin79
Related Servers
Alternatives to Jira + Confluence MCP
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to read, search, create, edit, comment, transition, plan sprints, and write pages in Jira and Confluence Server or Data Center, with personal access tokens sent only to the user's own host.MIT
- AlicenseCqualityBmaintenanceEnables MCP clients to work with self-hosted Jira Server / Data Center 8.x through entity-based core tools, JSON-declared plugin tools, and bundled Zephyr Scale. It supports issue, comment, worklog, attachment, project, user, link, watcher, agile, and test management operations using Basic Auth or PAT with runtime field discovery.9714 npmMIT
- AlicenseAqualityDmaintenanceMCP server for Confluence Server/Data Center (self-hosted) that gives LLM agents access to search, read, create/edit pages, comments, labels, and attachments via the Confluence REST API.1523 npmISC
- AlicenseNot gradedqualityCmaintenanceA cloud-hosted MCP server that gives AI tools secure, real-time access to Atlassian Cloud products such as Jira, Confluence, Bitbucket, and Loom, enabling search, summarization, content creation, and workflow automation through natural language.Apache 2.0
TDQS
B3.3/5.0
Scored across 27 tools
Disambiguation4/5
Most tools target a clear resource/action pair, and the jira_/confluence_ prefixes keep domains separate. The main ambiguity is the two generic *_rest tools, which overlap with every dedicated tool, though their escape-hatch role is clearly described.
Naming Consistency5/5
All tools use snake_case with a domain prefix and predictable verb_noun phrasing (list/get/create/update/delete/add/search). The generic REST tools are the only nonstandard action but still fit the prefix convention.
Tool Count3/5
27 tools is on the heavy side, especially with generic REST catch-alls that can perform many of the same operations as dedicated tools. The dual Jira+Confluence scope makes the breadth defensible, but it is still borderline heavy.
Completeness4/5
Core issue/page CRUD, search, comments, transitions, projects, spaces, boards, sprints, worklogs, and attachments listing are covered. Gaps like comment update/delete, worklog listing/removal, issue-link removal, and attachment mutation exist but are workable through the generic REST tools.
Maintenance
ActivityMaintained
ResponsivenessNo issues