Gk Cli
Give your agent GitKraken CLI powers to manage repos, pull requests, and issues across GitHub, GitLab, and Bitbucket from one MCP stdio server.
Overview
GitKraken gk-cli MCP is a Build-phase MCP server that exposes GitKraken CLI control of repos, PRs, and issues across major Git hosts via local stdio.
What is this MCP server?
- Manage repos, PRs, and issues across GitHub, GitLab, Bitbucket, and more
- npm package @gitkraken/gk version 3.1.64 with stdio transport
- CLI entry: positional argument mcp for MCP mode
- Manifest version 3.1.64 aligned with package version
- Source repo: github.com/gitkraken/gk-cli
- Transport: stdio
- 1 npm package with mcp positional argument
Community signal: 416 GitHub stars.
What problem does it solve?
Your agent can patch files locally but cannot open PRs, read issues, or manage remotes without constant context switching to the browser.
Who is it for?
Solo developers already using or willing to use GitKraken CLI who want multi-host Git automation in Claude Code or Cursor.
Skip if: Workflows that forbid local CLI MCP, or teams standardized on a single host API with no GitKraken setup.
What do I get? / Deliverables
After installing @gitkraken/gk and enabling MCP mode, your agent can run GitKraken-backed repo and PR/issue actions from the IDE.
- Local stdio MCP server backed by GitKraken CLI
- Agent-accessible repo, PR, and issue operations across configured remotes
Recommended MCP Servers
Journey fit
How it compares
Cross-forge GitKraken CLI MCP integration, not an in-repo git skill or code-review methodology pack.
Common Questions / FAQ
Who is com.gitkraken/gk-cli for?
It is for builders who use GitKraken’s CLI and want MCP-connected agents to handle repos, PRs, and issues on GitHub, GitLab, Bitbucket, and similar hosts.
When should I use com.gitkraken/gk-cli?
Use it during build when you want the agent to create or update PRs, manage issues, and inspect repos without leaving the coding session.
How do I add com.gitkraken/gk-cli to my agent?
Install npm package @gitkraken/gk (3.1.64), configure MCP to run gk with positional argument mcp over stdio, and complete GitKraken auth for your remotes.