mcp-jira-server-custom

sabbir-47/mcp-jira-server-custom

3.2

If you are the rightful owner of mcp-jira-server-custom and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

A comprehensive Model Context Protocol (MCP) server for JIRA integration, providing AI assistants with powerful JIRA automation capabilities.

Tools
7
Resources
0
Prompts
0

MCP JIRA Server

A comprehensive Model Context Protocol (MCP) server for JIRA integration, providing AI assistants with powerful JIRA automation capabilities including advanced comment analysis and professional HTML report generation.

πŸš€ Overview

This project provides a powerful MCP JIRA Server (mcp_jira_server.py) - a Model Context Protocol server for AI assistant integration with JIRA, featuring intelligent comment analysis, stale issue detection, and executive-ready HTML reports.

πŸ“‹ Features

Core MCP Tools

  • πŸ” Search Issues - JQL-based issue searching with flexible filters
  • πŸ“‹ Get Issue Details - Comprehensive issue information with optional comment analysis
  • 🧠 Comment Analysis - AI-powered comment analysis with keyword detection and sentiment insights
  • ✨ Create Issues - New issue creation with full metadata support
  • πŸ“ Update Issues - Modify existing issues and status transitions
  • πŸ’¬ Add Comments - Smart commenting with assignee mentions and dry-run/live modes
  • πŸ•’ Find Stale Issues - Advanced stale issue detection with component/project filtering
  • πŸ“Š Generate Reports - Professional HTML reports with interactive charts and executive summaries

πŸ› οΈ Setup

# Install dependencies
pip install -r requirements.txt

# Set environment variables
export JIRA_URL="your-jira-domain"
export JIRA_TOKEN="your-bearer-token"  # Get from JIRA β†’ Settings β†’ Personal Access Tokens

# Run server
python mcp_jira_server.py

🎯 Usage Examples

πŸ“‹ Single Issue Analysis

Basic Issue Details:

"Get details for OCPBUGS-12345"

Issue with Comment Analysis:

"Get details for OCPBUGS-12345 with comment analysis"
"Analyze the comments on OCPBUGS-12345 to understand the current status"

Pure Comment Analysis:

"Analyze comments on OCPBUGS-12345"
"What's the sentiment and activity on OCPBUGS-12345 comments?"
"Check OCPBUGS-12345 for escalation indicators in comments"

πŸ•’ Stale Issues Detection

Basic Stale Issues:

"Find stale bugs with no comments in the last 5 days"
"Show me issues that haven't been updated in 7 days"

Project-Specific Analysis:

"Find stale bugs in OCPBUGS project with no comments over 3 days"
"Search only in ACM project for stale issues over 10 days"

Release-Specific Analysis:

"Find stale issues in 4.14 and 4.16 releases with no comments over 5 days"
"Show me stale bugs in 4.18 release that need attention"

Component-Specific Analysis:

"Find stale issues only in GitOps ZTP component for 4.14 and 4.16 releases"
"Show me stale bugs in Networking SR-IOV component over 7 days"

πŸ“Š Professional Report Generation

Basic Report Generation:

"Generate a stale issues report for 4.14 and 4.16 releases with no comments over 5 days"
"Create an HTML report for stale bugs in GitOps ZTP component"

Advanced Report Generation:

"Generate executive report for stale issues in OCPBUGS project over 7 days with comment analysis"
"Create comprehensive report for 4.18 release bugs with no activity in 10 days"

Custom Report Parameters:

"Generate report for GitOps ZTP component in 4.14, 4.16, 4.18 releases, 
 bugs only, no comments over 5 days, save as 'gitops_analysis.html'"

πŸ’¬ Smart Commenting

Basic Comments:

"Add comment to OCPBUGS-123 asking for status update"
"Comment on OCPBUGS-456 that this needs verification"

Comments with Assignee Mentions:

"Add comment to OCPBUGS-123 mentioning the assignee for update"
"Comment on OCPBUGS-456 asking assignee about timeline"

Dry-Run Comments (Preview):

"Show me how the comment would look for OCPBUGS-123 before posting"
"Preview comment for OCPBUGS-456 with assignee mention"

πŸ“Š HTML Report Generation

Sample Report

πŸ“Š Executive Dashboard View:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚  GitOps ZTP Stale Issues Analysis - Executive Dashboard     β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚                                                             β”‚
β”‚  πŸ“‹ Executive Summary                                       β”‚
β”‚  Current State: 16 out of 20 issues (80%) in stale state  β”‚
β”‚  Critical Risk: 7 issues (44%) never triaged               β”‚
β”‚  Business Impact: 367-day abandoned issue needs closure    β”‚
β”‚                                                             β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”          β”‚
β”‚  β”‚   16    β”‚ β”‚   80%   β”‚ β”‚   20    β”‚ β”‚   5+    β”‚          β”‚
β”‚  β”‚ Stale   β”‚ β”‚ Stale   β”‚ β”‚ Total   β”‚ β”‚ Days    β”‚          β”‚
β”‚  β”‚ Issues  β”‚ β”‚ Rate    β”‚ β”‚Analyzed β”‚ β”‚Thresholdβ”‚          β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜          β”‚
β”‚                                                             β”‚
β”‚  πŸ“Š Interactive Charts: [Status] [Age] [Release Impact]    β”‚
β”‚                                                             β”‚
β”‚  🚨 Critical Actions Required:                             β”‚
β”‚  β€’ Close OCPBUGS-42657 (367 days old)                     β”‚
β”‚  β€’ Verify 3 MODIFIED issues (108+ days stale)             β”‚
β”‚  β€’ Triage 7 issues with zero comments                     β”‚
β”‚                                                             β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

πŸ“ Report Location: report/stale_issues_report.html
🌐 View: Open in any web browser for full interactive experience

🧠 AI-Powered Comment Analysis

The MCP server includes sophisticated comment analysis that provides actionable insights:

Analysis Features

  • πŸ”‘ Keyword Detection - Identifies urgency, status, and problem indicators
  • πŸ“Š Activity Patterns - Categorizes comment frequency and engagement
  • 🚨 Escalation Detection - Flags issues requiring management attention
  • πŸ‘₯ Author Analysis - Tracks unique contributors and collaboration patterns
  • ⏰ Timeline Analysis - Maps comment activity over time

Sample Comment Analysis Output

πŸ” Comment Analysis for OCPBUGS-12345
Issue: ZTP spoke cluster creation fails intermittently
Status: MODIFIED

πŸ“Š Analysis Overview:
   β€’ Total Comments: 8
   β€’ Unique Authors: 3
   β€’ Activity Pattern: Moderate activity
   β€’ Last Activity: 2024-10-01T14:30:00Z

πŸ”‘ Keywords Detected:
   🚨 Urgency: critical, blocker
   βœ… Status: workaround, patch
   ⚠️ Problems: failing, error

🚨 Escalation Indicators:
   β€’ Recent escalation language detected

πŸ’¬ Recent Comments Analysis:
   1. John Doe (2024-10-01): This is still failing after the patch...
   2. Jane Smith (2024-09-28): Applied workaround but need permanent fix...

πŸ€– AI Assistant Insights:
   β€’ 🚨 Urgency keywords detected - prioritize this issue
   β€’ ⚠️ This issue shows escalation patterns - may need management attention
   β€’ πŸ‘₯ High collaboration (3 authors) - complex issue

This analysis helps AI assistants and users quickly understand issue context, urgency levels, and required actions.

⭐ Key Features

  • 🧠 AI-Powered Analysis - Intelligent comment analysis with keyword detection
  • πŸ“Š Executive Reports - Professional HTML reports with interactive charts
  • πŸ•’ Advanced Stale Detection - Flexible project/component/release filtering
  • πŸ’¬ Smart Comments - Assignee mentions, dry-run preview, live posting
  • ⚑ High Performance - Optimized API calls (96% fewer requests)
  • πŸ›‘οΈ Safety First - Dry-run by default, secure bearer token authentication
  • πŸ”§ Modular Design - Reusable comment analysis across all tools

πŸ”§ Configuration

VariableDescription
JIRA_URLJIRA instance URL
JIRA_TOKENBearer token from JIRA settings

πŸš€ MCP Integration

Claude-CLI

Add to the mcp server to claude:

claude mcp add "custom-jira" "./bin/python" "<PATH>/mcp_jira_server.py"

Verification

Add to the mcp server to claude:

>> claude mcp get jira 
⏺ Bash(claude mcp get jira)
  ⎿  jira:                                                 
       Scope: Local config (private to you in this project)
       Status: βœ“ Connected
     … +6 lines (ctrl+o to expand)

⏺ The jira MCP server is configured locally for this project, running ./bin/python 
  mcp_jira_server.py via stdio and is currently connected.

πŸ› οΈ Available MCP Tools

ToolDescriptionKey Parameters
jira_search_issuesSearch issues with JQLjql, max_results
jira_get_issueGet detailed issue infoissue_key, include_comment_analysis
jira_analyze_issue_commentsPure comment analysisissue_key, days_threshold
jira_create_issueCreate new issuesproject_key, summary, description
jira_update_issueUpdate existing issuesissue_key, fields, transition
jira_add_commentAdd comments with mentionsissue_key, comment, mention_assignee, mode
jira_find_stale_issuesFind stale issuesdays_threshold, affects_versions, override_components
jira_generate_stale_issues_reportGenerate HTML reportsdays_threshold, affects_versions, report_filename

Keep your JIRA projects moving with AI-powered automation and intelligent analysis πŸš€