Gitkraken Mcp

Created By
gitkraken11 days ago
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. It works with all the providers you would expect from the GitKraken software suite such as GitHub, GitLab, Azure DevOps, Bitbucket, Jira and more. Built by the team behind GitLens, the Git tool that 48 million developers chose, from first-time contributors to enterprise teams at Netflix and Adobe.
Overview

GitKraken MCP Server

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. It works with all the providers you would expect from the GitKraken software suite such as GitHub, GitLab, Azure DevOps, Bitbucket, Jira and more. Built by the team behind GitLens, the Git tool that 48 million developers chose, from first-time contributors to enterprise teams at Netflix and Adobe.

The GitKraken MCP Server is available on macOS, Windows, and Linux systems and works in VS Code, Cursor, Windsurf, Claude Desktop, Kiro, JetBrains, and more.

If you want to read more about the MCP server, you can check out the introductory blog post.

Table of Contents

Tools

Tools are the primary purpose of the MCP server. They are a set of finely curated commands that AI can use to interact with GitKraken without exploding your context. Some of those tools include: issues_assigned_to_me, gitlens_commit_composer, and pull_request_create_review. A full list of tools can be found in the GitKraken Help Center's Tools Reference.

Prompts

Prompts are the secondary purpose of the MCP server. They are a set of carefully crafted instructions that AI can use to understand how to use the tools, when to use them, and what information to provide when using them. A full list of prompts can be found in the GitKraken Help Center's Prompts Reference.

Installation

There are a few ways of installing the MCP server. Regardless of which installation method you choose, you may still need to configure your AI tools to work with the MCP server. You can find a set of instructions on the Help Center's MCP Getting Started guide.

GitLens

GitLens is by far the easiest way of installing the MCP server. Simply download and install GitLens into a supported IDE (VS Code, Cursor, etc) and the MCP server will be installed alongside it. Once you have GitLens installed, you can start using the tools right away.

NPM

You can also install and use the MCP server via npm. You can find the package on the npm registry.

The installation process details may vary by AI tool, but the general gist is that you will replace the MCP server JSON config with something that looks like this:

{
  "mcpServers": {
    "GitKraken": {
      "args": ["@gitkraken/gk", "mcp"],
      "command": "npx",
      "type": "stdio"
    }
  }
}

CLI

macOS

gk is available from Homebrew with the following command:

Homebrew:

brew install gitkraken-cli

Or download it from the releases page and add it to your binaries folder:

mv ~/Downloads/gk /usr/local/bin/gk

Linux / Ubuntu

Get it from the Snap Store

gk is available as a downloadable binary from the releases page. Once you have it, add it to your binaries folder:

mv ~/Downloads/gk /usr/local/bin/gk

Or create a new directory, move the binary and add it to $PATH:

mkdir "$HOME/cli"
mv ~/Downloads/gk "$HOME/cli"
export PATH="$HOME/gk:$PATH"

You can also [download][releases page] your corresponding package (.deb, .rpm) and install it with:

sudo apt install ./gk.deb

or

sudo rpm -i ./gk.rpm

Windows

gk is available from [Winget][winget] with the following command:

winget install gitkraken.cli

Troubleshooting

gk from Oh-My-Zsh

If you installed the gitkraken-cli and are using Oh-My-Zsh you can run into a small aliasing issue. Oh-My-Zsh has gitk aliased as gk by default and that can create some problems. To fix this, type in your terminal:

unalias gk

Support

If you run into any issues, double check if we have the problem covered in our Help Center.

You can give feedback and report bugs on GitHub by submitting an issue.

If you would like to reach out to Support directly, you can submit a ticket

Server Config

{
  "mcpServers": {
    "GitKraken": {
      "command": "npx",
      "args": [
        "@gitkraken/gk",
        "mcp"
      ],
      "type": "stdio"
    }
  }
}
Project Info
Created At
11 days ago
Updated At
11 days ago
Author Name
gitkraken
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Context Repo Mcp Server
@ContextRepo

*One workspace for your prompts, documents, and collections — accessible from every AI client you use.* Context Repo is an AI context management platform for capturing, organizing, versioning, and searching the knowledge artifacts you use with AI tools. This MCP server exposes **28 tools** that give Claude, Cursor, ChatGPT, Factory, Windsurf, Codex, Claude Code, and any other MCP-compatible client direct read-and-write access to your personal workspace — no copy-paste, no context loss between conversations. ## Features - **Prompts** — Full CRUD with version history, rollback, and semantic search across your prompt library - **Documents** — Markdown and plain-text storage with automatic chunking and 1536-dim vector embeddings - **Collections** — Named folders that group prompts and documents into project-scoped contexts - **Catalog Search** — `find_items` returns ranked results across prompts, documents, and collections in a single call (semantic by default, literal fallback) - **Deep Search** — Hierarchical document navigation: search ranked passages, then expand up to parents, down to children, or sideways to siblings for token-efficient exploration of long content - **Version History** — Every content edit creates a new version; restore any prompt or document to any previous state - **Real-time Sync** — Changes propagate instantly via Convex live queries; AI clients always see the latest content - **ChatGPT Apps Ready** — `search` and `fetch` are OpenAI Apps SDK Company-Knowledge eligible; `find_items` carries an optional `ui://` resource for inline result rendering ## Tools (28 total) | Category | Tools | |---|---| | User Info (1) | `get_user_info` | | Prompts (7) | `search_prompts` · `read_prompt` · `create_prompt` · `update_prompt` · `delete_prompt` · `get_prompt_versions` · `restore_prompt_version` | | Documents (7) | `list_documents` · `get_document` · `create_document` · `update_document` · `delete_document` · `get_document_versions` · `restore_document_version` | | Collections (7) | `list_collections` · `get_collection` · `create_collection` · `update_collection` · `delete_collection` · `add_to_collection` · `remove_from_collection` | | Catalog (1) | `find_items` | | Deep Search (3) | `deep_search` · `deep_read` · `deep_expand` | | ChatGPT Apps (2) | `search` · `fetch` | ## Authentication Two ways to connect: 1. **API Key** — Generate a scoped `gm_*` key at [contextrepo.com/dashboard/settings](https://contextrepo.com/dashboard/settings). Per-key permissions: `prompts.read`, `prompts.write`, `documents.read`, `documents.write`, `documents.scrape`. Sent as `Authorization: Bearer gm_...`. 2. **Clerk OAuth 2.0** — RFC 9728 protected-resource metadata at `/.well-known/oauth-protected-resource/mcp`, RFC 8414 authorization-server metadata at `/.well-known/oauth-authorization-server`. Standard OAuth flow for clients that support it. ## Use Cases - **Prompt library that follows you.** Stop copy-pasting prompts between Claude, Cursor, and ChatGPT. Maintain one canonical version, retrieve it from any client. - **Personal knowledge base.** Save research articles, documentation, and AI conversations with the [Context Repo Chrome Extension](https://contextrepo.com/chrome-extension), then pull them in as grounded context inside your AI tools. - **Project-scoped collections.** Separate workspaces per client, repo, or topic so an AI assistant only sees what's relevant to the task at hand. - **Version-controlled prompts.** Track how prompts evolve, A/B test variants, and roll back when an "improvement" turns out worse. - **Long-document exploration.** Deep Search navigates book-length documents passage by passage instead of dumping them into context — every chunk carries parent/child/sibling links the agent can walk. ## Compatibility Streamable HTTP transport, MCP spec ≥ 2025-03-26. Verified with Claude Desktop, Cursor, ChatGPT (via the OpenAI Apps SDK), Factory, Windsurf, Codex, Claude Code, VS Code (Continue), and Amp. Any MCP-compatible client should work. ## Resources - Website: [contextrepo.com](https://contextrepo.com) - Documentation: [contextrepo.com/docs](https://contextrepo.com/docs) - Pricing & free trial: [contextrepo.com/pricing](https://contextrepo.com/pricing) - Agent discovery: [contextrepo.com/llms.txt](https://contextrepo.com/llms.txt) - API reference: [contextrepo.com/openapi.json](https://contextrepo.com/openapi.json)

21 hours ago
Datagrout

a day ago