MCP JIRA Server
Related Servers
Alternatives to MCP JIRA Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA Model Context Protocol server that enables AI applications to interact with Jira issues, projects, and workflows through a standardized interface.2Apache 2.0
- AlicenseCqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact with Jira Cloud instances, providing capabilities for issue management, project listing, and JQL search.176 npm2MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that integrates with Atlassian's Jira and Confluence, enabling AI assistants to interact with these tools directly through features like issue management, page creation, and content search.131MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol (MCP) server that connects AI assistants to Jira and Confluence, enabling search, create, update, and comment operations with rich Markdown-to-ADF conversion.1539 npm2MIT
- FlicenseDqualityDmaintenanceA Model Context Protocol server that enables integration with JIRA, allowing users to interact with JIRA tasks and issues through Claude AI assistant.33-
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact with Jira, allowing for project management tasks such as listing projects, searching issues, creating tickets, and managing sprints through natural language queries.776 npm2TypeScriptMIT
TDQS
Scored across 4 tools
Three JIRA-related tools have clear distinct purposes: create, search, and update issues. However, the 'echo' tool is completely unrelated to the JIRA domain, which creates a minor but noticeable ambiguity in the toolset's overall purpose. The JIRA tools themselves are well-differentiated.
The three JIRA tools follow a consistent verb_noun pattern with underscores (create_jira_issue, search_jira_issues, update_jira_issue). However, the 'echo' tool breaks this pattern by using a single word without the JIRA prefix, creating mixed conventions within the set. The naming is readable but not fully consistent.
With only 4 tools, the count feels thin for a JIRA server, especially given that one tool ('echo') is unrelated to JIRA. For a domain as rich as JIRA issue management, having just three core tools (create, search, update) is borderline minimal, lacking expected operations like delete, get details, or comment management.
The toolset has significant gaps for JIRA issue management. While it covers create, search, and update, it lacks essential operations like deleting issues, retrieving specific issue details, adding comments, or managing attachments. The inclusion of an unrelated 'echo' tool further dilutes the domain coverage, making the surface incomplete for typical JIRA workflows.