MCP Server - Jira & Git Integration logo

MCP Server - Jira & Git Integration

by kashuta

This project provides an MCP server that integrates with Jira and Git to automate common development workflows. It watches for file changes in a specified Git repository, checks the current branch for a Jira issue key, and updates the corresponding Jira issue status.

View on GitHub

Last updated: N/A

What is MCP Server - Jira & Git Integration?

This is an MCP server that automates development workflows by integrating Jira and Git. It monitors a Git repository for file changes, extracts Jira issue keys from branch names, and updates the corresponding Jira issue status.

How to use MCP Server - Jira & Git Integration?

  1. Clone the repository. 2. Install dependencies using npm install. 3. Configure environment variables in a .env file with your Jira and Git credentials. 4. Run the server using npm run dev for development or npm run build and npm start for production. 5. Interact with the server using an MCP client via STDIN/STDOUT to call tools like getJiraIssue, createGitBranchAndPR, and updateJiraStatus.

Key features of MCP Server - Jira & Git Integration

  • Automatic Jira Status Updates based on Git changes

  • MCP Tool Integration for Jira and Git interactions

  • Configurable environment variables for Jira/Git credentials

  • Creation of Git feature branches and Pull Request templates from Jira issues

Use cases of MCP Server - Jira & Git Integration

  • Automating Jira status updates when code changes are made

  • Creating feature branches and pull requests directly from Jira issues

  • Integrating with AI agents or IDE extensions via MCP

  • Streamlining development workflows by connecting Jira and Git

FAQ from MCP Server - Jira & Git Integration

What is the purpose of the JIRA_UPDATE_STATUS environment variable?

It defines the target status in Jira to which the issue will be updated when file changes are detected in the Git repository.

How do I generate a Jira API token?

Go to your Atlassian Account Settings > Security > Create and manage API tokens.

What is the expected format for branch names to extract Jira issue keys?

The expected format is type/KEY-123-description, where KEY-123 is the Jira issue key.

What happens when a file change is detected?

The server checks the current branch name for a Jira issue key, verifies if there are uncommitted Git changes, and if both conditions are met, attempts to update the corresponding Jira issue's status.

What are the available MCP tools?

The available MCP tools are getJiraIssue, createGitBranchAndPR, and updateJiraStatus. They allow MCP clients to retrieve Jira issue details, create Git branches and PRs, and manually update Jira issue statuses, respectively.