GitKraken · Codex
Add the GitKraken MCP server to Codex
Git operations plus issues and pull requests across GitHub, GitLab, Jira and Azure DevOps through the gk CLI.
1. Add the server
Run in your terminal
# ~/.codex/config.toml [mcp_servers.gitkraken] command = "npx" args = ["-y", "@gitkraken/gk", "mcp"]
Scopes, env vars, OAuth and limits: Codex MCP config guide
2. Sign in
Run codex mcp login <name> to complete OAuth for a remote server. GitKraken runs locally; set any credentials GitKraken asks for before starting Codex.
3. Try it
Ask Codex 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.
- · Each server is a [mcp_servers.<name>] table in config.toml.
- · Use enabled_tools or disabled_tools to keep the tool list short.
Get the weekly agent stack update
New official MCP servers, spec changes and harness releases, checked against the source. One email a week, no fluff.
FAQ
- How do I add the GitKraken MCP server to Codex?
- Run: # ~/.codex/config.toml …. Run codex mcp login <name> to complete OAuth for a remote server.
- 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 Codex
Work at GitKraken?
Feature GitKraken across the directory and its category from $49/month.
Reviewed Oct 21, 2026. Command generated from the registry record and checked against Codex's documented syntax.