MCP Server - Jira & Git Integration
@kashuta
MCP Server - Jira & Git Integration
Overview
What is MCP Server - Jira & Git Integration?
This MCP server 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. It is for developers using Jira and Git who want to streamline their workflow.
How to use MCP Server - Jira & Git Integration?
Clone the repository, run npm install, configure environment variables in a .env file, then start the server with npm run dev (development) or npm run build && npm start (production). An MCP client connects via STDIN/STDOUT to call the provided tools.
Key features of MCP Server - Jira & Git Integration
- Automatic Jira status updates on file changes
- MCP tool integration for Jira and Git actions
- Configurable via environment variables
Use cases of MCP Server - Jira & Git Integration
- Automatically update a Jira issue status when code changes are detected on a feature branch
- Retrieve Jira issue details using the
getJiraIssuetool - Create a Git feature branch and pull request template from a Jira issue
FAQ from MCP Server - Jira & Git Integration
What MCP tools does the server expose?
It exposes three tools: getJiraIssue, createGitBranchAndPR, and updateJiraStatus. Each takes issue IDs and optionally a new status.
How does automatic Jira status updating work?
The server monitors the directory specified by GIT_REPO_PATH for file changes. When a change is detected, it checks the current branch name for a Jira issue key (e.g., PROJ-123) and, if uncommitted Git changes exist, updates the Jira issue status to the value defined in JIRA_UPDATE_STATUS.
What environment variables are required?
Required variables: JIRA_BASE_URL, JIRA_EMAIL, JIRA_API_TOKEN, JIRA_PROJECT_KEY, JIRA_UPDATE_STATUS, GIT_REPO_PATH, GIT_DEFAULT_BRANCH. Optional: DEBUG and LOG_LEVEL.
What are the runtime requirements?
Node.js and npm are required. The server must be run in an environment with access to a Git repository (local path) and a Jira instance (cloud).
How is authentication handled?
Jira authentication uses an API token generated from Atlassian Account Settings, provided via the JIRA_API_TOKEN environment variable.