Gitkraken Mcp

by gitkraken

442 downloads

Not rated

GitHub

Developer Tools

About

Details

Author: gitkraken
Downloads: 442
Categories: Developer Tools

- Tools: a curated set of commands for AI to interact with GitKraken (e.g., issues_assigned_to_me, gitlens_commit_composer, pull_request_create_review).
- Prompts: crafted instructions that teach AI how and when to use the tools.
- Multiple installation methods: GitLens, npm, and standalone CLI.
- Cross-platform support: macOS, Windows, Linux.
- Works with major git providers and IDEs.
- Built by the team behind GitLens, trusted by millions.

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name Gitkraken Mcp

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

From the repository

You can install the Gitkraken Mcp server via GitLens (simplest), via npm (npx @gitkraken/gk mcp), or via the CLI (Homebrew on macOS, Snap or .deb/.rpm on Linux, Winget or binary on Windows). After installation, you may still need to configure your AI tools; instructions are in the Help Center’s Getting Started guide.

`gitkraken_workspace_list`

Lists all Gitkraken workspaces

`gitlens_launchpad`

Gitlens Launchpad. Gets your open pull requests prioritized by what needs attention: ready to merge, has conflicts, awaiting review, etc. Helpful for checking todos, outstanding tasks, or deciding what to work on next.

`gitlens_start_review`

Gitlens Start Review. Creates a dedicated worktree and reviews your PR with an AI agent.

`gitlens_start_work`

Gitlens Start Work. Creates a work based on an issue. This tool will create a branch and link it with the issue, keeping context visible throughout your work.

`issues_add_comment`

Add a comment to an issue

`issues_assigned_to_me`

Fetch issues assigned to the user. Set assigned_to_me=false to broaden the result to all visible issues. To filter server-side by assignee, set unassigned=true for issues with no assignee, or assigned_to=<user> for issues assigned to a specific person (assigned_to_me, unassigned and assigned_to are mutually exclusive). Narrow results further with repository_name/repository_organization (GitHub), project/issue_type (Jira), or is_closed.

`issues_create`

Create a new issue. For Jira, repository_name is the project key. For Linear, repository_organization is the team UUID, key, or name.

`issues_get_detail`

Retrieve detailed information about a specific issue by its unique ID. For Jira Epics, the response includes a childIssues array containing all issues linked to the epic.

`pull_request_assigned_to_me`

Search pull requests where you are the author or assignee. Set reviewer to true to also include pull requests where you are a requested reviewer (github and gitlab only).

`pull_request_create`

Create a new pull request

`pull_request_create_review`

Create a review for a pull request

`pull_request_get_comments`

Get all the comments in a pull requests

`pull_request_get_detail`

Get an specific pull request

`repository_get_file_content`

Get file content from a repository

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "gitkraken mcp": {
            "GitKraken": {
                "command": "npx",
                "args": [
                    "@gitkraken/gk",
                    "mcp"
                ],
                "type": "stdio"
            }
        }
    }
}

McpServers

{
    "GitKraken": {
        "command": "npx",
        "args": [
            "@gitkraken/gk",
            "mcp"
        ],
        "type": "stdio"
    }
}

GitKraken MCP Server

The GitKraken MCP Server turns your AI assistant into a context-aware development partner by connecting it to git history, branches, issues, pull requests, and multi-repo workflows through GitKraken. It works with all the providers you would expect from the GitKraken software suite such as GitHub, GitLab, Azure DevOps, Bitbucket, Jira and more. Built by the team behind GitLens, the Git tool that 48 million developers chose, from first-time contributors to enterprise teams at Netflix and Adobe. The GitKraken MCP Server is available on macOS, Windows, and Linux systems and works in VS Code, Cursor, Windsurf, Claude Desktop, Kiro, JetBrains, and more. If you want to read more about the MCP server, you can check out the introductory blog post.

- Tools - Prompts - Installation - Troubleshooting - Support

Tools

Tools are the primary purpose of the MCP server. They are a set of finely curated commands that AI can use to interact with GitKraken without exploding your context. Some of those tools include: issues_assigned_to_me, gitlens_commit_composer, and pull_request_create_review. A full list of tools can be found in the GitKraken Help Center's Tools Reference.

Prompts

Prompts are the secondary purpose of the MCP server. They are a set of carefully crafted instructions that AI can use to understand how to use the tools, when to use them, and what information to provide when using them. A full list of prompts can be found in the GitKraken Help Center's Prompts Reference.

Installation

There are a few ways of installing the MCP server. Regardless of which installation method you choose, you may still need to configure your AI tools to work with the MCP server. You can find a set of instructions on the Help Center's MCP Getting Started guide.

GitLens

GitLens is by far the easiest way of installing the MCP server. Simply download and install GitLens into a supported IDE (VS Code, Cursor, etc) and the MCP server will be installed alongside it. Once you have GitLens installed, you can start using the tools right away.

NPM

You can also install and use the MCP server via npm. You can find the package on the npm registry. The installation process details may vary by AI tool, but the general gist is that you will replace the MCP server JSON config with something that looks like this: ``

json
{
  "mcpServers": {
    "GitKraken": {
      "args": ["@gitkraken/gk", "mcp"],
      "command": "npx",
      "type": "stdio"
    }
  }
}



CLI


macOS

 is available from Homebrew with the following command:

Homebrew:

bash
brew install gitkraken-cli



Or download it from the releases page and add it to your binaries folder:

bash
mv ~/Downloads/gk /usr/local/bin/gk



---

Linux / Ubuntu

 is available as a downloadable binary from the releases page. Once you have it, add it to your binaries folder:

bash
mv ~/Downloads/gk /usr/local/bin/gk



Or create a new directory, move the binary and add it to $PATH:

bash
mkdir "$HOME/cli"
mv ~/Downloads/gk "$HOME/cli"
export PATH="$HOME/gk:$PATH"



You can also [download][releases page] your corresponding package (

.deb, .rpm

) and install it with:

bash
sudo apt install ./gk.deb

or

bash
sudo rpm -i ./gk.rpm



---

Windows

 is available from [Winget][winget] with the following command:

bash
winget install gitkraken.cli



Troubleshooting


gk from Oh-My-Zsh


If you installed the

gitkraken-cli and are using Oh-My-Zsh you can run into a small aliasing issue. Oh-My-Zsh has gitk aliased as gk

 by default and that can create some problems. To fix this, type in your terminal:

bash
unalias gk

Support

If you run into any issues, double check if we have the problem covered in our Help Center. You can give feedback and report bugs on GitHub by submitting an issue. If you would like to reach out to Support directly, you can submit a ticket

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Jump to

Setting up with Highlight

From the repository

gitkraken_workspace_list

gitlens_launchpad

gitlens_start_review

gitlens_start_work

issues_add_comment

issues_assigned_to_me

issues_create

issues_get_detail

pull_request_assigned_to_me

pull_request_create

pull_request_create_review

pull_request_get_comments

pull_request_get_detail

repository_get_file_content

Claude Desktop / Cursor

McpServers

GitKraken MCP Server

Table of Contents

Tools

Prompts

Installation

GitLens

NPM

CLI

macOS

Linux / Ubuntu

Windows

Troubleshooting

gk from Oh-My-Zsh

Support

Install

More like this

Sentry

Github

Git

GitLab

Context 7

Playwright

`gitkraken_workspace_list`

`gitlens_launchpad`

`gitlens_start_review`

`gitlens_start_work`

`issues_add_comment`

`issues_assigned_to_me`

`issues_create`

`issues_get_detail`

`pull_request_assigned_to_me`

`pull_request_create`

`pull_request_create_review`

`pull_request_get_comments`

`pull_request_get_detail`

`repository_get_file_content`