REPOSITORY COLLABORATION / GitKraken
GitKraken MCP Server
GitKraken's official MCP server connects assistants to git history, branches, issues, pull requests and multi-repo workflows across GitHub, GitLab, Azure DevOps, Bitbucket and Jira. Ships inside the gk CLI (npm @gitkraken/gk), installs via GitLens, and is packaged for the Docker MCP Catalog.
“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.”
01 / THE REASONING
Why this made the selection.
- The publisher ships its own MCP server in the gk CLI with a curated tool set (issues_assigned_to_me, gitlens_commit_composer, pull_request_create_review) instead of one-tool-per-endpoint sprawl.
- The repository publishes Docker MCP Catalog packaging whose tools.json generator intentionally excludes app-only tools that MCP agents must not call, and the image runs as a non-root user against explicitly mounted repositories.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- GitKraken MCP repository at pinned revision de51c47b5238ef529ec842d62a850ff689a53adf: README documents the tool and prompt surface, npm and GitLens installation, and Docker packaging; package.json pins @gitkraken/gk 3.1.70 and names the repository as Docker MCP Catalog packaging and validation; LICENSE is MIT (Axosoft, LLC dba GitKraken).
- Dockerfile at the pinned revision: node:22-bookworm-slim base, runs as the built-in non-root node user, npm ci --omit=dev, with git safe.directory configured for mounted repositories.
- GitKraken introductory blog post and Help Center tools reference: the server is built by the team behind GitLens, and the full tool and prompt lists are documented in the Help Center.
- tools.json at the same commit
Our findings
- The MCP server ships inside the gk CLI; the public repository packages and validates it for the Docker MCP Catalog, regenerating tools.json from the pinned CLI version so the catalogued surface stays in sync.
- The generator intentionally excludes app-only tools that MCP agents must not call, keeping the exposed surface agent-safe.
- tools.json at this commit lists 29 tools (counted from the file): git_add, git_blame, git_branch, git_checkout, git_commit, git_commit_composer, git_fetch, git_graph, git_log_or_diff, git_pull, git_push, git_resolve, git_stash, git_status, git_worktree, 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.
- The README’s Tools section names gitlens_commit_composer as an example; tools.json at the same commit lists git_commit_composer and no gitlens_commit_composer.
- configExample now keeps the README’s key order (args, command, type). The values are unchanged.
Not established by this review
- No GitKraken account was linked and no issue, branch or pull-request operation was executed.
- No tool from tools.json was called; the generator that rebuilds tools.json from the Docker image was not run.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
npx @gitkraken/gk mcpCopying does not execute this command. It may retrieve a newer version than the reviewed source.
- Install GitLens into a supported IDE — the MCP server is installed alongside it — or use the npm package @gitkraken/gk directly.
- Add the mcpServers block running `npx @gitkraken/gk mcp` to the client configuration.
- Authenticate with your GitKraken account when the client prompts, then ask for your assigned issues to verify the connection.
- The command above is the command and args of the README’s mcpServers block (npx with @gitkraken/gk mcp), not a separate installer. It was not run.
Before you start
- A GitKraken account for cloud features (issues, pull requests, provider operations).
- Node.js 22 or later for the npm path, or Docker for the catalog image.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"GitKraken": {
"args": [
"@gitkraken/gk",
"mcp"
],
"command": "npx",
"type": "stdio"
}
}
}04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/gitkraken/mcp/blob/de51c47b5238ef529ec842d62a850ff689a53adf/README.md
Supports: summary, upstreamDescription, bestFor, limitations, install, configExample, compatibility
https://github.com/gitkraken/mcp/blob/de51c47b5238ef529ec842d62a850ff689a53adf/package.json
Supports: repository, revision, language, whySelected
https://github.com/gitkraken/mcp/blob/de51c47b5238ef529ec842d62a850ff689a53adf/LICENSE
Supports: license
https://www.gitkraken.com/blog/introducing-gitkraken-mcp
Supports: homepage, summary, whySelected
https://help.gitkraken.com/mcp/mcp-tools-reference/
Supports: limitations, bestFor
- GitKraken MCP tools.json ↗Checked
https://github.com/gitkraken/mcp/blob/de51c47b5238ef529ec842d62a850ff689a53adf/tools.json
Supports: Tool list, Write tools, limitations, access