GitKraken MCP Server

The GitKraken MCP Server gives your agent your Git operations, issue tracking and pull request workflows across GitHub, GitLab, Jira and Azure DevOps. It's part of the GitKraken CLI (gk) and runs on your machine. What you can do with it - Check status, stage and commit, push and stash, and list or create branches and worktrees - Find out who last changed a line and why, and read commit logs and diffs - Fetch the issues assigned to you, read an issue's details and comment on it - Find pull requests you're assigned to, wrote or are reviewing, read their details and comments, and create a review - Get a file's content from a repository and list your GitKraken workspaces - With GitLens, start work on an issue or a pull request review in a new worktree, and open Launchpad or the Commit Composer How it connects It's the gk mcp command of the GitKraken CLI, which installs with Homebrew (brew install gitkraken-cli), Winget, the Snap Store, npm (@gitkraken/gk) or a download from its releases page. Sign in once with gk auth login, then add gk mcp to your agent as a local (stdio) server. GitKraken's docs cover Claude Desktop, Claude Code, Codex, Gemini CLI, Cursor, VS Code, Antigravity and more. In VS Code, Cursor and other VS Code-based editors, GitLens 17.5 or later bundles the server and installs it for you. Good to know - The Git tools work on every GitKraken plan. Issue and pull request tools, and private repositories, need Pro or higher; enterprise trackers such as Jira Data Center and Azure DevOps Server need Advanced or higher. - The GitLens tools need GitLens in your editor. - You can turn individual tools on or off in your agent.