docs: README Claude Code snippet should use --pull=always #35

New issue

Closed

opened 2026-09-30 18:50:53 +00:00 by piscis · 1 comment

piscis commented

2026-09-30 18:50:53 +00:00

Owner

What to build

The README's Claude Code setup should add --pull=always, so that Consumers on :3 actually follow the major line.

Right now both the .mcp.json snippet (README ~L77–83) and the claude mcp add line (~L93) run docker run -i --rm … code.vicoli.de/vicoli-oss/forgejo-mcp:3. Docker pulls :3 only when it isn't cached locally. After the first pull, a Consumer stays on that version until they run docker pull by hand. This repo's own dogfood config (.mcp.json, #31 / PR #34) already uses --pull=always for this reason. Being offline costs nothing extra, because the server won't start anyway without a reachable Forgejo.

Target shape for the .mcp.json snippet (keep the README's variable handling, and add the flag only):

"args": [
  "run", "-i", "--rm", "--pull=always",
  "-e", "FORGEJO_URL",
  "-e", "FORGEJO_ACCESS_TOKEN",
  "code.vicoli.de/vicoli-oss/forgejo-mcp:3"
]

Add one short sentence explaining why the flag is there (:3 plus --pull=always gives you new minor/patch releases and Rebuilds on each session start).

Out of scope: the one-off initialize check (~L52/L60) and HTTP mode (~L108). In HTTP mode a long-lived container gets updated by restarting it, which is a different story. Also out of scope: the dogfood config's FORGEJO_URL default, which is specific to vicoli.

Acceptance criteria

The README's .mcp.json snippet and the claude mcp add line both include --pull=always
The README explains in one sentence why the flag is there
The README snippet and this repo's .mcp.json differ only in the FORGEJO_URL default

Blocked by

None (can start immediately)

## What to build The README's Claude Code setup should add `--pull=always`, so that Consumers on `:3` actually follow the major line. Right now both the `.mcp.json` snippet (README ~L77–83) and the `claude mcp add` line (~L93) run `docker run -i --rm … code.vicoli.de/vicoli-oss/forgejo-mcp:3`. Docker pulls `:3` only when it isn't cached locally. After the first pull, a Consumer stays on that version until they run `docker pull` by hand. This repo's own dogfood config (`.mcp.json`, #31 / PR #34) already uses `--pull=always` for this reason. Being offline costs nothing extra, because the server won't start anyway without a reachable Forgejo. Target shape for the `.mcp.json` snippet (keep the README's variable handling, and add the flag only): ```json "args": [ "run", "-i", "--rm", "--pull=always", "-e", "FORGEJO_URL", "-e", "FORGEJO_ACCESS_TOKEN", "code.vicoli.de/vicoli-oss/forgejo-mcp:3" ] ``` Add one short sentence explaining why the flag is there (`:3` plus `--pull=always` gives you new minor/patch releases and Rebuilds on each session start). Out of scope: the one-off `initialize` check (~L52/L60) and HTTP mode (~L108). In HTTP mode a long-lived container gets updated by restarting it, which is a different story. Also out of scope: the dogfood config's `FORGEJO_URL` default, which is specific to vicoli. ## Acceptance criteria - [ ] The README's `.mcp.json` snippet and the `claude mcp add` line both include `--pull=always` - [ ] The README explains in one sentence why the flag is there - [ ] The README snippet and this repo's `.mcp.json` differ only in the `FORGEJO_URL` default ## Blocked by None (can start immediately)

piscis added the

ready-for-agent

label

2026-09-30 18:50:55 +00:00

piscis commented

2026-09-30 18:51:59 +00:00

Author

Owner

Triaged: checked against main. README L79 (.mcp.json snippet) and L93 (claude mcp add) lack --pull=always; the dogfood .mcp.json already has it. Fully specified, docs-only change → ready-for-agent.

Triaged: checked against main. README L79 (`.mcp.json` snippet) and L93 (`claude mcp add`) lack `--pull=always`; the dogfood `.mcp.json` already has it. Fully specified, docs-only change → ready-for-agent.

piscis referenced this issue from a commit

2026-09-30 18:54:10 +00:00

docs: adopt the Image via .mcp.json with --pull=always (#32, #35)

piscis referenced this issue from a pull request that will close it,

2026-09-30 18:54:19 +00:00

docs: adopt the Image via .mcp.json with --pull=always (#32, #35) #36

piscis closed this issue

2026-09-30 18:56:09 +00:00

piscis referenced this issue from a commit

2026-09-30 18:56:10 +00:00

Merge pull request 'docs: adopt the Image via .mcp.json with --pull=always (#32, #35)' (#36) from piscis/32-claude-setup-update into main