F
licenseNot graded
qualityB
maintenanceMCP server that provides AI assistants with access to Jira Cloud for issue management, search, and workflow operations.
-
Jira MCP OAuth gateway
Related Servers
Alternatives to Jira MCP OAuth gateway
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 gradedqualityBmaintenanceMCP server for Atlassian Confluence and Jira, enabling AI assistants to search, create, and update issues and pages via natural language.MIT
- AlicenseCqualityCmaintenanceAn MCP server that enables AI assistants to interact with JIRA, allowing for querying issue details, creating and updating work items, and managing attachments through a standardized interface.124MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI assistants to interact with Atlassian Jira and Confluence across Cloud and Server/Data Center environments. It supports tasks like searching and summarizing documentation, managing Jira issues, and creating content through natural language.MIT
- AlicenseAqualityBmaintenanceMCP server for Jira Cloud that lets AI agents search, read, and write Jira issues using your own Atlassian account and API token, with write operations gated behind explicit opt-in.525 npmMIT
TDQS
B3/5.0
Scored across 17 tools
Disambiguation2/5
Multiple aliases (get_task/get_ticket, read_task/read_ticket) create redundancy and confusion. Agents may struggle to choose the correct tool for retrieving issue data. The two attachment tools are similar but distinct in source.
Naming Consistency3/5
Most tools follow verb_noun pattern (e.g., create_ticket, list_boards), but inconsistencies exist: jira_login instead of login_jira, and usage of both 'get' and 'read' for similar retrieval functions. The lengthy get_only_ticket_name_and_description breaks the pattern.
Tool Count3/5
17 tools is slightly above the well-scoped range (3-15). While the number covers Jira operations, the presence of duplicate aliases (4 tools for ticket retrieval) inflates the count without adding value.
Completeness3/5
Core operations like CRUD for issues, JQL search, and project/board listing are present. However, critical gaps exist: no tool for transitioning issue status (workflow), and no direct way to manage issue types or sprints. Alias tools further reduce effective coverage.
Maintenance
ActivityMaintained
ResponsivenessNo issues