New v1.1.3Use gitaiflow as a Claude Desktop ExtensionInstall the extension

Install gitaiflow with Claude Desktop (Docker)

Run the gitaiflow MCP server in Docker and connect it to the Claude Desktop Client over stdio, for environments that cannot run the native binary or the packaged extension.

Requires repository access

gitaiflow is a private repository, so this path is for repo collaborators, not a general public install. If you don’t have access, use the Claude Desktop Extension instead — or request access.

Request repository access

Most Claude Desktop Client users should install the Claude Desktop Extension instead.

Clone the gitaiflow repository (requires repo access)

$git clone https://gitlab.com/codefleet-labs/gitaiflow.git
$cd gitaiflow

Build the MCP image

$docker build --no-cache -f Dockerfile.mcp -t gitaiflow-mcp:local .

Test the stdio command in a terminal first

$docker run --rm -i \
$  --env-file .mcp.env \
$  -e MCP_TRANSPORT=stdio \
$  -e MCP_WORKSPACE=/workspace \
$  -e MCP_ALLOWED_WORKSPACES=/workspace \
$  -e GITAIFLOW_BINARY=/app/bin/gitaiflow \
$  -v "$HOME/.gitaiflow:/root/.gitaiflow" \
$  -v "$MCP_HOST_WORKSPACE:/workspace" \
$  -v "/path/to/gitaiflow-linux-arm64:/app/bin/gitaiflow:ro" \
$  gitaiflow-mcp:local

Add it to claude_desktop_config.json

{
  "mcpServers": {
    "gitaiflow-mcp": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "--env-file", "/absolute/path/to/gitaiflow/.mcp.env",
        "-e", "MCP_TRANSPORT=stdio",
        "-e", "MCP_WORKSPACE=/workspace",
        "-e", "MCP_ALLOWED_WORKSPACES=/workspace",
        "-e", "GITAIFLOW_BINARY=/app/bin/gitaiflow",
        "-v", "/absolute/path/to/home/.gitaiflow:/root/.gitaiflow",
        "-v", "/absolute/path/to/parent-workspace:/workspace",
        "-v", "/absolute/path/to/gitaiflow-linux-arm64:/app/bin/gitaiflow:ro",
        "gitaiflow-mcp:local"
      ]
    }
  }
}

Who this is for

This is the same Docker image as Docker MCP, wired to one local Claude Desktop Client over stdio instead of a shared HTTP service.
Most Claude Desktop Client users get a simpler, zero-Docker setup from the packaged extension — use this only when the native binary or extension can’t run in your environment.

Claude Desktop (Docker) configuration

Claude Desktop uses stdio, so there is no port mapping — the command above is spawned directly by Claude Desktop, the same way it would spawn a native binary.

AI settings still come from ~/.gitaiflow/config.env, mounted into the container exactly as in the Docker MCP setup.

Claude Desktop Extension (recommended for most users)

Replace every absolute path with paths on your machine. The /workspace mount must be the parent workspace, not a single repository, if you want to select several repositories by name. Use gitaiflow-linux-amd64 on x86_64.

Workspaces and repository selection

The Docker mount at /workspace, together with MCP_ALLOWED_WORKSPACES, identifies the parent workspace. The tool path argument selects one Git repository inside it, and the selected directory must itself be a Git repository root.

Multi-repository layout

Multiple repositories

Mount the parent directory that contains all your repositories to /workspace — one -v flag, not one per repository. For example, -v "/Users/<user>/projects:/workspace" if projects/ holds paperclip/, VoiceStudio/, and issuetracker/, each with its own .git.
gitaiflow selects a specific repository by name using the tool’s path argument — a request naming paperclip resolves to /workspace/paperclip.

Go deeper

Claude Desktop MCP setup (docs)Docker MCP verification guide (docs)

DjangoPlay · gitaiflow