Unified DevOps MCP Server

A Model Context Protocol (MCP) server that integrates JIRA, GitLab, and SonarQube for seamless DevOps workflows.

Features

JIRA Integration

• Get assigned issues
• Get issue details
• Create issues (Task, Story, Bug)
• Add worklogs and comments
• Assign issues to users
• Search users
• Update issue fields
• Transition issues between statuses
• Confluence page search

GitLab Integration

• Get current branch with JIRA ID extraction
• Commit changes with JIRA format
• Push changes to remote
• Create merge requests with auto-generated descriptions
• Review merge requests with code analysis
• List merge requests

SonarQube Integration

• Discover accessible projects
• Get project quality metrics
• Get project issues by severity/type

Installation

npm install -g unified-devops-mcp

Configuration

Create a .env file with the following variables:

# JIRA Configuration
JIRA_URL=https://your-domain.atlassian.net
[email protected]
JIRA_API_TOKEN=your-jira-api-token

# Confluence (Optional)
CONFLUENCE_SPACE_KEY=YOUR_SPACE

# GitLab Configuration
GITLAB_URL=https://gitlab.com
GITLAB_TOKEN=glpat-xxxxxxxxxxxxx
GITLAB_PROJECT_ID=12345678

# SonarQube Configuration
SONARQUBE_URL=https://sonarqube.company.com
SONARQUBE_TOKEN=squ_xxxxxxxxxxxxx

Usage with Claude Desktop

Add to your Claude Desktop configuration:

MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "unified-devops": {
      "command": "unified-devops-mcp",
      "env": {
        "JIRA_URL": "https://your-domain.atlassian.net",
        "JIRA_EMAIL": "[email protected]",
        "JIRA_API_TOKEN": "your-token",
        "GITLAB_URL": "https://gitlab.com",
        "GITLAB_TOKEN": "your-token",
        "GITLAB_PROJECT_ID": "12345678",
        "SONARQUBE_URL": "https://sonarqube.company.com",
        "SONARQUBE_TOKEN": "your-token"
      }
    }
  }
}

Available Tools

JIRA Tools

• jira_get_my_issues - Get issues assigned to current user
• jira_get_issue_details - Get complete issue details
• jira_create_issue - Create new JIRA issue
• jira_add_worklog - Add worklog to issue
• jira_add_comment - Add comment to issue
• jira_assign_issue - Assign issue to user
• jira_search_users - Search users by name/email
• jira_update_issue - Update issue fields
• jira_get_transitions - Get available transitions
• jira_transition_issue - Transition issue status
• confluence_search_pages - Search Confluence pages

GitLab Tools

• gitlab_get_current_branch - Get current branch and JIRA ID
• gitlab_commit_changes - Commit with JIRA format
• gitlab_push_changes - Push to remote
• gitlab_create_merge_request - Create MR with description
• gitlab_review_merge_request - Review MR and attach summary
• gitlab_list_merge_requests - List merge requests

SonarQube Tools

• sonar_discover_projects - Discover accessible projects
• sonar_get_project_metrics - Get quality metrics
• sonar_get_project_issues - Get project issues

Development Workflows

Story Development Cycle

1. Extract JIRA ID from story
2. Create feature branch: feature/DLG-XXXX from develop
3. Develop with mandatory test cases
4. Commit with format: DLG-XXXX # message
5. Push changes
6. Create MR to develop with code review

Commit Message Standard

Format: JIRA-ID # message

Example: DLG-7365 # Add tag cloud component

MR Title Standard

Format: JIRA-ID # title

Example: DLG-7365 # Add Tag Cloud Component to Home Page

Best Practices

• MANDATORY: Write test cases for ALL code changes
• For website projects: Create tests in packages/__test__/
• For page.tsx routes: Ensure loading.tsx and layout.tsx are handled
• Always check if modifications impact other components
• Raise MRs to develop branch with code review summary

License

MIT

Support

For issues and feature requests, please visit our GitHub repository.