git_add_or_commitLABSCO SUMMARY
One connection for the repository and the tracker above it.
Most git servers stop at the working tree. This one carries the issue and pull-request side too, across four trackers, so what am I meant to be working on and commit this are answered without the agent changing tools halfway through.
What it is
GitKraken's MCP server, shipped inside the GitKraken CLI and inside GitLens. It runs over stdio as gk mcp and carries both the local repository and the trackers you have connected, so an agent can move between the commit and the ticket above it.
What you get
- Git: stage and commit, branch, checkout, log or diff, push, stash, read status, blame a file, and list or add worktrees
- Issues: the ones assigned to you, the detail on any one of them, and a comment written back
- Pull requests: the ones where you are author, assignee or reviewer, their detail and comments, and a review created from the conversation
- GitLens workflows: open Commit Composer or Launchpad, start work on an issue, start a PR review
- File contents from a repository, and a list of your GitKraken workspaces
- Individual tools switched on or off in your own IDE or agent configuration
Requirements
The GitKraken CLI, installed and signed in with gk auth login. In VS Code, Cursor, Windsurf and Trae, GitLens 17.5 or later installs the server for you. Issue, pull-request and private-repository tools need Pro or higher; enterprise trackers such as Jira Data Center and Azure DevOps Server need Advanced.
Setup effort
Follow the published steps — brew install gitkraken-cli
USE CASES
01
Starting on the issue you were assigned
Fetch the issues assigned to you, read the one that matters, and branch for it — GitLens can open the same work from its own start-work flow.
02
Reviewing a pull request you were added to
Find the PRs where you are the reviewer, read the detail and the comments already on it, then leave the review from the same thread.
03
Getting a messy working tree committed
Read the status, look at what actually changed, stage and commit the parts that belong together, then push.
04
Finding out who last touched a line
Blame the file and read the commits around it, so a question about a change has an answer before anyone has to be asked.
22 tools
Listed in project docs. Your client may show a different list.
git_blamegit_branchgit_checkoutgit_log_or_diffgit_pushgit_stashgit_statusgit_worktreegitkraken_workspace_listgitlens_commit_composergitlens_launchpadgitlens_start_reviewgitlens_start_workissues_add_commentissues_assigned_to_meissues_get_detailpull_request_assigned_to_mepull_request_create_reviewpull_request_get_commentspull_request_get_detailrepository_get_file_contentBEFORE YOU INSTALL
What to know first
Tools you get
22 tools named in the project's documentation.
INSTALLATION
Connect your client
Server setup
TERMINAL
brew install gitkraken-cli
gk auth login
claude mcp add -t stdio gitkraken gk mcpMCP Clients
Claude Desktop, Cursor, JetBrains IDEs, Antigravity
JSON
{
"mcpServers": {
"gitkraken": {
"command": "gk",
"args": [
"mcp"
]
}
}
}Codex
Settings → MCP Servers → Add Server → STDIO — Name: gitkraken, Command: gk, Arguments: mcp
Amazon Q Developer
Configure MCP Server → + — Name: gitkraken, Transport: stdio, Command: gk, Arguments: mcp
Kiro
KIRO · JSON
{
"mcpServers": {
"gitkraken": {
"command": "gk",
"args": [
"mcp"
],
"env": {},
"disabled": false,
"autoApprove": []
}
}
}
