F
licenseA
qualityC
maintenanceEnables Claude Code to read and write issues on the Testing Platform via natural language, including listing projects, filtering issues, creating and updating issues, and adding comments.
9
-
jdra-mcp
by minssd2
Related Servers
Alternatives to jdra-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables Claude Code to interact with JIRA through natural language, supporting issue creation, updates, searches, and workflow transitions, designed for enterprise intranets.2278 npmApache 2.0
- AlicenseCqualityCmaintenanceEnables AI-powered automated testing, security scanning, code review, and maintenance tasks directly within Claude Code or desktop.124MIT
- AlicenseBqualityDmaintenanceEnables natural language interactions with GitLab via Claude Code, supporting MR reviews, issue management, pipeline monitoring, and branch comparisons.37871 npmMIT
- FlicenseNot gradedqualityFmaintenanceIntegrates with Claude Code to execute AI-powered code analysis and workflow automation, supporting pre-defined scenarios like code review and security audit.5-
- FlicenseAqualityDmaintenanceEnables users to interact with Backlog issues directly from VSCode/GitHub Copilot or Claude Desktop, providing tools to retrieve issues, list comments, and add comments.3-
TDQS
B3.4/5.0
Scored across 12 tools
Disambiguation3/5
Several tools have overlapping purposes: jdra_create_issue and jdra_create_and_register_issue (one is a superset of the other), and jdra_import_jira_issue vs jdra_register_jira_to_weekly_report similarly overlap. Descriptions clarify the differences, but an agent could easily misselect when only the atomic action is needed. The search_* tools and whoami are clearly distinct.
Naming Consistency4/5
All tools share the jdra_ prefix and use snake_case, with a generally predictable verb_noun pattern (search_projects, create_issue, add_issue_to_weekly_report). Minor deviations include jdra_whoami and the compound verb in create_and_register_issue, but overall the naming is consistent and readable.
Tool Count5/5
With 12 tools, the server covers a focused set of operations for JDRA/Jira integration and weekly report management. Each tool serves a specific function or a clearly documented shortcut, and the count is well within the typical 3-15 range for a cohesive MCP server.
Completeness3/5
The core workflow—searching reference data, previewing/importing Jira issues, creating JDRA issues, and registering them to weekly reports—is well covered. However, there are notable gaps: no get/list/update/delete for imported or created issues, and no way to remove an issue from a weekly report. This limits full lifecycle management within the server.
Maintenance
ActivityMaintained
ResponsivenessNo issues