MCP.so
Sign In

Git Jira MCP Server

@1pone

About Git Jira MCP Server

这是一个用于获取 Jira 需求信息的 MCP 服务器,基于当前 Git 分支名自动获取对应的 Jira 需求详情。

Basic information

Category

Version Control

Runtime

node

Transports

stdio

Publisher

1pone

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "git-jira": {
      "command": "npx",
      "args": [
        "-y",
        "git-jira-mcp-server"
      ],
      "env": {
        "JIRA_INSTANCE_URL": "https://your-domain.atlassian.net",
        "JIRA_USER_EMAIL": "[email protected]",
        "JIRA_API_KEY": "your_api_token",
        "JIRA_BRANCH_PATTERNS": "dev_[a-zA-Z]+-([A-Z]+-\\d+),feature/[a-zA-Z]+-([A-Z]+-\\d+),bugfix/[a-zA-Z]+-([A-Z]+-\\d+),dev_[a-zA-Z]+_([A-Z]+-\\d+)"
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Git Jira MCP Server?

A Model Context Protocol (MCP) server that automatically detects the current Git branch name, extracts a Jira issue ID from it, and fetches the corresponding Jira issue details. It provides title, description, status, priority, and assignee information directly in your MCP-compatible client. Aimed at developers who want to see Jira context without leaving their coding environment.

How to use Git Jira MCP Server?

Configure the server in your MCP client’s mcp.json file with the command npx -y git-jira-mcp-server and set the required environment variables: JIRA_INSTANCE_URL, JIRA_USER_EMAIL, JIRA_API_KEY, and optionally JIRA_BRANCH_PATTERNS. The server will then match your current Git branch against the configured patterns and fetch the corresponding Jira issue.

Key features of Git Jira MCP Server

  • Automatically extracts Jira ID from current Git branch
  • Fetches Jira issue title, description, status, priority, assignee
  • Configurable branch naming patterns via environment variables
  • Clear error messages for branch format, API failure, missing env vars
  • Lightweight, no persistent storage – fetches live data

Use cases of Git Jira MCP Server

  • Quickly view the Jira ticket you're working on without leaving your IDE
  • Get Jira issue context directly in MCP‑enabled chat or assistant tools
  • Automate branch‑to‑issue mapping across multiple repositories

FAQ from Git Jira MCP Server

How does Git Jira MCP Server identify the Jira issue?

It reads the current Git branch name and extracts the Jira ID using pattern matching. The default patterns support formats like dev_[name]-[JIRA-ID], feature/[name]-[JIRA-ID], and bugfix/[name]-[JIRA-ID].

What environment variables are required?

JIRA_INSTANCE_URL, JIRA_USER_EMAIL, and JIRA_API_KEY are mandatory. JIRA_BRANCH_PATTERNS is optional and allows custom branch‑to‑ID extractors.

What happens if the branch name doesn't match any pattern?

The server returns a clear error indicating a branch name format mismatch. It also handles API request failures and missing environment variables with distinct messages.

How do I obtain a Jira API token?

Visit [https://id.atlassian.com/manage-profile/security/api-tokens](https

Comments

More Version Control MCP servers