GitKraken MCP Server
Official GitKraken MCP server from the gk CLI: git, pull requests and issues across GitHub, GitLab, Bitbucket and Jira
- 465 ★ on the repository
- Last commit
Broad access
Why this level
- The agent commits, pushes and creates pull requests and issues on your behalf in GitHub, GitLab, Bitbucket and Jira
- Provider tokens are stored in `gk` and give access to repositories and issues
Install
- Works in
Manual install
brew install gitkraken-climacOS; on Windows `winget install gitkraken.cli`, on Linux a binary or package from the releases page.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent commits, pushes and creates pull requests and issues on your behalf in GitHub, GitLab, Bitbucket and Jira
- Provider tokens are stored in `gk` and give access to repositories and issues
This is third-party code. Review the repository files before installing.
What it does
GitKraken CLI (`gk`) is the console edition of GitKraken built around work items: a feature or task for which you work across several repositories at once, as in a monorepo. The `gk work commit --ai` and `gk work pr create --ai` commands compose commit messages and pull request descriptions with AI. The CLI includes a local MCP server that starts with `gk mcp`. The server wraps git, GitHub and Jira actions and gives models tools for GitKraken APIs and features. The MCP registry describes it as a server for managing repositories, pull requests and issues across GitHub, GitLab, Bitbucket and more. Connection instructions for specific AI apps are collected in the GitKraken Help Center. Authentication goes through the CLI: `gk auth login` and `gk provider` for provider tokens. The CLI is available on macOS, Windows and Linux.
Who it is for. Developers who run tasks in Git hosts and Jira through GitKraken and want to hand commits, pull requests and work items to an agent.
Good fit when
- One feature touches three repositories and the agent creates a shared work item and commits changes to each
- AI composes the commit message and pull request description from the changes and you only approve
- You need to find Jira issues and related GitHub pull requests without switching tabs
- The team lives on several hosts at once: GitHub, GitLab and Bitbucket
Not a fit when
- You only need plain git on one repository: the stock command line and the GitHub MCP are enough
- You need the server's source code: the repository holds releases and documentation but not source
- You have no GitKraken account: signing in with `gk auth login` is required for most commands
Example request
Create a work item for the report export feature across two repositories, commit the changes with an AI message and prepare a pull requestMCP
- Transport
- stdio
- Authentication
- OAuth
Limitations
The repository holds releases and documentation, there is no source code and no license in the metadata. The server is part of `gk` and requires the installed CLI and a sign-in to a GitKraken account. Provider tokens are added with `gk provider`. Detailed instructions for connecting specific AI apps are in the Help Center, and the README points there without ready configs. On macOS the first launch makes you confirm opening the downloaded file in the security settings. The tool set depends on the CLI version and the MCP registry lists 3.1.77.
How to disable. Remove the gitkraken block from the client config (`claude mcp remove gitkraken`), sign out and remove provider tokens in `gk provider`.
FAQ
How do I install GitKraken CLI?
On macOS: `brew install gitkraken-cli`. On Windows: `winget install gitkraken.cli`. On Linux take a binary or a `.deb` or `.rpm` package from the releases page, and there is also a Snap Store package.
How do I start the MCP server?
With `gk mcp`, it works over stdio. In the MCP registry the server is published as the `@gitkraken/gk` npm package with the argument `mcp`.
Which hosts does the server work with?
GitHub, GitLab, Bitbucket and others, plus Jira. Provider tokens are added with `gk provider`.
What is a work item in gk?
A feature or task for which you work across several repositories at once. A work item is created with `gk work create "name"` and the current directory is added to it automatically.
Where do I find instructions for my AI app?
In the GitKraken Help Center, in the section on the CLI MCP server. The repository points there and adds an introductory post on the GitKraken blog.
Discussion
No questions or reviews yet.
Related
MCP serversA git MCP server with 28 tools: an agent clones, commits, branches, merges, rebases and manages worktrees in local repositories.
An MCP server for GitLab and self-hosted instances: projects, merge requests, issues, pipelines, wiki and releases
gh-mcp runs the GitHub MCP server as a gh extension on your GitHub CLI login, with no personal token in client settings.
GitVerse MCP: code review and PRs
GitVerse MCP Server
A GitVerse MCP server with 25 bitbucket-mcp-style tools: pull requests, inline code review with verdicts and running GitVerse Actions CI pipelines
GitFlic MCP built on gitflic-cli
gitflic-cli MCP-сервер
An MCP server with 76 typed tools over a GitFlic CLI: merge requests, issues, releases, package registry, with group filters and a read-only mode
An MCP server that turns GitHub Projects v2 into a work queue for agents: they claim tasks, report progress and spend a budget.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| GitKraken MCP Server (this card) | yes | OAuth | 465 | |
| GitHub MCP Server | no | key is optional | 34,418 | GitHub's official server for that host only, with no work items across repositories and no Jira |
| GitLab MCP Server | no | API key | 2,103 | a server for one GitLab rather than a shared layer over several hosts and Jira |
README in short
The text presents `gk` as GitKraken on the command line, explains work items and says there is an MCP server inside. Next come a table of contents, command help, a workflow from `gk auth login` to `gk work pr create --ai`, installation for three systems and a troubleshooting section.