GitKraken MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| app_tool_boxA | Dispatch app-only helper actions for MCP apps. App-only; agents must not call this tool. |
| app_update_user_preferencesA | Update GitKraken CLI user preferences for MCP apps. App-only; agents must not call this tool. |
| git_add_or_commitA | Add file contents to the index (git add ) OR record changes to the repository (git commit -m [files...]). Use the 'action' parameter to specify which action to perform. |
| git_blameA | Show what revision and author last modified each line of a file (git blame ). |
| git_branchB | List or create branches (git branch). |
| git_checkoutB | Switch branches or restore working tree files (git checkout ). |
| git_fetchA | Download objects and refs from another repository (git fetch). |
| git_graphA | Show the commit graph for a repository (git log --graph), will open a UI if client supports it. |
| git_log_or_diffA | Show commit logs or changes between commits (git log --oneline or git diff). |
| git_pullB | Fetch from and integrate with another repository or a local branch (git pull). |
| git_pushA | Update remote refs along with associated objects (git push). |
| git_stashB | Stash the changes in a dirty working directory (git stash). |
| git_statusA | Show the working tree status (git status), will open a UI if client supports it. |
| git_worktreeB | List or add git worktrees (git worktree ). |
| gitkraken_workspace_listA | Lists all Gitkraken workspaces |
| gitlens_commit_composerA | Gitlens Commit Composer. Organize your changes into well-formed commits with clear messages and descriptions. Useful for breaking large changes into smaller commits. |
| gitlens_launchpadA | Gitlens Launchpad. Gets your open pull requests prioritized by what needs attention: ready to merge, has conflicts, awaiting review, etc. Helpful for checking todos, outstanding tasks, or deciding what to work on next. |
| gitlens_start_reviewB | Gitlens Start Review. Creates a dedicated worktree and reviews your PR with an AI agent. |
| gitlens_start_workB | Gitlens Start Work. Creates a work based on an issue. This tool will create a branch and link it with the issue, keeping context visible throughout your work. |
| issues_add_commentB | Add a comment to an issue |
| issues_assigned_to_meA | Fetch issues assigned to the user |
| issues_get_detailA | Retrieve detailed information about a specific issue by its unique ID. For Jira Epics, the response includes a childIssues array containing all issues linked to the epic. |
| pull_request_assigned_to_meA | Search pull requests where you are the author or assignee. Set reviewer to true to also include pull requests where you are a requested reviewer (github and gitlab only). |
| pull_request_createC | Create a new pull request |
| pull_request_create_reviewB | Create a review for a pull request |
| pull_request_get_commentsB | Get all the comments in a pull requests |
| pull_request_get_detailB | Get an specific pull request |
| repository_get_file_contentC | Get file content from a repository |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Git Graph | Git graph viewer UI (MCP Apps HTML resource) |
| Git Status | Git status viewer UI (MCP Apps HTML resource) |
TDQS
Scored across 28 tools
Most tools have distinct purposes, but git_add_or_commit and git_log_or_diff combine two actions into one tool, potentially causing confusion. The app-only tools are clearly marked, reducing ambiguity.
Naming convention is mixed: git_ prefix for Git commands, gitkraken_ and gitlens_ for features, and issues_/pull_request_ for issue/PR tools. While each subgroup is consistent, the overall pattern is inconsistent.
28 tools is on the high side for a single server, covering Git, GitKraken features, and issue/PR management. It may be slightly overwhelming but still within a reasonable range for the broad domain.
The tool set covers major Git operations, GitKraken workflows, and issue/PR management well. Minor gaps include lack of git branch delete, issue listing by criteria beyond assigned, and merged git operations could be separate.