GitKraken · Cursor
Add the GitKraken MCP server to Cursor
Git operations plus issues and pull requests across GitHub, GitLab, Jira and Azure DevOps through the gk CLI.
1. Add the server
Paste into .cursor/mcp.json (project) or ~/.cursor/mcp.json (global)
{
"mcpServers": {
"gitkraken": {
"command": "npx",
"args": [
"-y",
"@gitkraken/gk",
"mcp"
]
}
}
}Scopes, env vars, OAuth and limits: Cursor MCP config guide
2. Sign in
Cursor prompts you to sign in the first time a remote OAuth server is used. GitKraken runs locally; set any credentials GitKraken asks for before starting Cursor.
3. Try it
Ask Cursor for something GitKraken can do. Git operations plus issues and pull requests across GitHub, GitLab, Jira and Azure DevOps through the gk CLI. Approve the first tool call and check the result before allowing write actions automatically.
- · Remote servers take a url; local servers take command and args.
- · Values can reference ${env:NAME} so secrets stay out of the file.
FAQ
- How do I add the GitKraken MCP server to Cursor?
- Run: { …. Cursor prompts you to sign in the first time a remote OAuth server is used.
- Is this the official GitKraken MCP server?
- Yes. It is published by GitKraken as com.gitkraken/gk-cli in the official MCP registry.
- Does the GitKraken MCP server need an API key?
- It runs locally from a package. See GitKraken's docs for any credentials it needs.
Links
GitKraken in other clients
More developer tools for Cursor
Built an MCP server? Get it listed everywhere →
Shipping an Android app? Google Play needs 12 testers for 14 days first. Get them with Tester Exchange →
Reviewed Oct 21, 2026. Command generated from the registry record and checked against Cursor's documented syntax.