Git MCP Server
Runs everyday git work on local repositories, from clone and commit to rebase, worktrees and push
Local git, pull request and issue tools from GitKraken's gk command-line program
Official · GitKraken Local · stdio Git and code hostingProductivity
83 popularity score ★ 463 ↓ 87k/wk
Opens the app, which asks before it adds the server.
npm i -g @gitkraken/gk
gk auth loginclaude mcp add gitkraken -- gk mcp{
"mcpServers": {
"gitkraken": {
"command": "gk",
"args": [
"mcp"
]
}
}
}{
"mcpServers": {
"gitkraken": {
"command": "gk",
"args": [
"mcp"
]
}
}
}{
"servers": {
"gitkraken": {
"type": "stdio",
"command": "gk",
"args": [
"mcp"
]
}
}
}[mcp_servers.gitkraken]
command = "gk"
args = ["mcp"]gemini mcp add --scope user gitkraken gk -- mcpThe GitKraken MCP Server is the `mcp` subcommand of `gk`, GitKraken's command-line program. Once `gk` is installed and signed in to a GitKraken account, an editor or agent starts it as `gk mcp` over stdio, and it runs on your own machine.
Its tools fall into four groups. Git tools work on the local repository: status, staging and committing, blame, branches, checkout, log and diff, stash, worktrees and push. Pull request and issue tools go through the integrations connected to your GitKraken account (GitHub, GitLab, Bitbucket, Jira and Azure DevOps are named in its docs) to list work assigned to you, read details and comments, post reviews and comments, and create issues and pull requests. A further tool lists GitKraken workspaces, and four GitLens tools open GitLens views such as Launchpad, the commit composer or a review worktree inside a VS Code-based editor.
The same server ships bundled with the GitLens extension (version 17.5 and later), which sets it up automatically in VS Code, Cursor, Windsurf and Trae; for other clients such as Claude Desktop, Claude Code, Gemini CLI or JetBrains AI Assistant you install the CLI and add `gk mcp` by hand, or run `gk mcp install <PLATFORM>`.
| Runtime | Node.js |
|---|
The `gk` CLI installed (Homebrew, Winget, Snap, .deb/.rpm, release binary, or `npm i -g @gitkraken/gk`) on macOS, Windows or Linux, and signed in with `gk auth login` to a GitKraken account. Issue, pull request and private-repository tools need a GitKraken Pro plan or higher; Jira Data Center and Azure DevOps Server need Advanced or higher; the GitLens tools need GitLens and a GitLens plan. On Windows, Cursor users need the current Visual C++ Redistributable.
Hosted pull request, issue and private-repository tools are behind paid GitKraken plans; on the free plan the git tools and public-repo file reads remain. The GitLens tools only work inside a VS Code-based editor with GitLens. Assigning a new pull request to yourself works on GitHub and GitLab only; Azure DevOps and Bitbucket return a warning. GitKraken says the tool list changes over time as tools are added and merged, and its npm README and help pages list slightly different tool names. Browser sign-in can hang in Safari and Brave, which block the localhost callback on port 1314.
Suits developers who already use GitKraken or GitLens and want one local server that covers local git plus pull requests and issues across several hosts and Jira, with sign-in handled once through their GitKraken account. Less suited to someone without a GitKraken account or a paid plan, since the hosted PR and issue tools need Pro or higher, or to anyone who wants a server talking directly to a single code host with its own token and no third-party account in between.
git_add_or_commitgit_blamegit_branchgit_checkoutgit_log_or_diffgit_pushgit_stashgit_statusgit_worktreegitkraken_workspace_listgitlens_commit_composergitlens_launchpadgitlens_start_reviewgitlens_start_workissues_add_commentissues_assigned_to_meissues_createissues_get_detailpull_request_assigned_to_mepull_request_createpull_request_create_reviewpull_request_get_commentspull_request_get_detailrepository_get_file_content