Jira Github MCP

What TamarEngel/jira-github-mcp MCP server does

TamarEngel/jira-github-mcp MCP server coordinates issue-based development across Jira, GitHub, and a local Git checkout. Jira tools retrieve individual issues, search with JQL, list issues assigned to the current user, and move issues between workflow statuses with optional comments. GitHub tools create pull requests and merge them using squash, merge, or rebase strategies, with an option to check CI status.

The local Git capability stages all changes, creates a commit, and pushes it to a branch. A branch can also be created from a Jira issue, supporting naming patterns such as feature/KAN-15. The documented workflow runs from issue discovery through branch creation, coding, commit and push, pull request creation, merge, and Jira status updates.

How it works

The server runs as a Python module and exposes tools over standard input/output to an MCP-compatible agent. The agent sends requests through the MCP server, which uses Jira and GitHub APIs for remote operations and performs Git commands against the configured local repository. Jira and GitHub API clients are asynchronous, while local Git actions operate on the repository path configured for the server.

MCP resources provide workflow guidance and current issue context. Internal prompts help guide agent behavior, but the available tools still determine which Jira, GitHub, and Git operations can be performed. The example client configuration starts the server with python -m src.server.server from the repository root.

Setup and configuration

TamarEngel/jira-github-mcp MCP server requires Python 3.10 or newer, Git on the system path, a Jira Cloud or self-hosted instance with REST API v3 access, and a GitHub repository with token-based API access. Install dependencies with uv sync or with the supplied pip requirements after creating a virtual environment.

Set these values in a .env file:

• JIRA_BASE_URL, without a trailing slash
• JIRA_EMAIL
• JIRA_API_TOKEN
• GITHUB_TOKEN
• GIT_REPO_URL
• GIT_DEFAULT_BRANCH
• GIT_REPO_LOCAL_PATH, optionally specifying the local checkout; otherwise the current working directory is used

The GitHub token should have only the permissions needed for the repository’s branch and pull-request operations. Configure the MCP client as a stdio server and set its working directory to the checked-out project path.

Tools and capabilities

The documented tools are:

• jira_get_issue: fetch an issue by key with configurable fields.
• jira_search_issues: search and paginate Jira results with JQL and filters.
• jira_get_my_issues: list issues assigned to the current user, with optional status or type filters.
• jira_transition_issue: move an issue to another workflow status and optionally add a comment.
• create_branch_for_issue: create a Git branch based on a Jira issue.
• git_commit_and_push: stage all changes, commit with a supplied message, and push to a branch.
• create_pull_request: open a GitHub pull request from a branch.
• merge_pull_request: merge a pull request with squash, merge, or rebase, optionally checking CI status.

TamarEngel/jira-github-mcp MCP server is suited to sprint execution, issue-driven feature work, bug fixes, and pull-request workflows where status updates should accompany code changes.

Limitations and notes

The documented implementation targets Jira and GitHub; GitLab support is listed as a future enhancement. Multi-repository workflows, reusable JQL templates, configurable automation rules, webhook synchronization, and AI-assisted commit or pull-request drafting are also future work rather than stated current capabilities.