Use gitaiflow from the Claude Desktop Client with one install command — no Docker, Python or MCP setup.
The packaged .mcpb extension bundles everything it needs.
curl -fsSL https://install.djangoplay.org/gitaiflow-mcp | bash
Open the downloaded .mcpb file with the Claude Desktop Client
.mcpb file to your Downloads folder and prints its path; open that file with the Claude Desktop Client to install..mcp.env is needed — the extension bundles the MCP server and the matching gitaiflow binary.No .mcp.env or manual MCP setup is needed. The extension uses the same AI settings as the AI-Native Binary — AI_PROVIDER, AI_API_KEY, AI_BASE_URL and AI_MODEL in ~/.gitaiflow/config.env — so set them once there.
origin.| Setting | Required | Notes |
|---|---|---|
| Allowed workspaces | Yes | Parent workspace(s) containing the Git repositories gitaiflow may analyze. |
| Git remote | No | Defaults to origin. |
| Developer Binary Path | No | Absolute path to your own gitaiflow executable. Leave empty to use the normal production binary. |
The extension uses the gitaiflow binary from the standard install location (~/.local/bin/gitaiflow on macOS & Linux, %LOCALAPPDATA%\Programs\gitaiflow on Windows). If none is found, it runs the official installer, and the download is verified against a signed checksum before it is trusted. Set Developer Binary Path to use your own build instead; if that file does not exist, the extension reports an error rather than falling back.
Give me the last generated gitaiflow change summary for my repository and show me the result.
Share my current gitaiflow_last_summary for my VoiceStudio repository.
Can you generate a change summary for my new changes using gitaiflow?
If several workspaces are configured, name the repository in your request so gitaiflow runs against that one only — for example: Can you generate release-notes for my paperclip repository?
| Tool | Required | Optional |
|---|---|---|
| gitaiflow_change_summary | remote | base_branch, path |
| gitaiflow_last_summary | — | path |
| gitaiflow_changelog | remote | since, until |
| gitaiflow_release_notes | — | path |
| gitaiflow_usage | — | scope, since, until |
| gitaiflow_list_models | — | free_only, as_json |
Use your repository’s real remote name for remote — it is never assumed to be origin. When path is used, it selects a Git repository inside the allowed workspace.