multiinstance-jira-mcp
Related Servers
Alternatives to multiinstance-jira-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Jira Cloud and Server/Data Center deployments for issue management, project tracking, and workflow automation. Supports multiple authentication methods including API tokens, OAuth 2.0, and personal access tokens.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
- AlicenseBqualityBmaintenanceEnables AI assistants to access and manage Jira boards, sprints, epics, issues, JQL searches, transitions, comments, worklogs, projects, users, and any REST endpoint across Jira Cloud and Data Center.4336 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseBqualityDmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage Jira tasks, issues, and projects using Atlassian's modern scoped API tokens, with safety features like read-only default and delete confirmation.69 npm4Apache 2.0
TDQS
Scored across 25 tools
Most tools map to a distinct resource+action, and instance-management tools (add/remove/set_default/login/logout) are clearly separable from issue operations. Minor overlap exists: jira_get_comments duplicates what jira_get_issue already returns, and jira_whoami partially overlaps jira_list_instances in surfacing instance/auth state.
Every tool uses the jira_ prefix with snake_case verb_noun phrasing (get_issue, create_issue, list_projects, add_attachment, copy_issue). The only mild deviation is jira_whoami, which is a standard, well-understood identifier rather than an inconsistency.
25 tools is at the heavy end but justified by covering multiple distinct areas: instance/auth management, issue CRUD, workflow transitions, and Jira Software metadata (boards, sprints, statuses, users). Nothing feels obviously redundant, though a few list_* tools could theoretically be consolidated.
Covers the core Jira lifecycle thoroughly: issue CRUD, transitions, assignment, comments, attachments, cross-instance copy, and metadata lookups. Gaps remain around comment update/delete, issue linking, worklogs, and attachment retrieval/removal, but these are minor for most agent workflows.