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.
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.
- 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
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.
One command — brew install gitkraken-cli