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

Merged

piscis merged 1 commit from piscis/32-claude-setup-update into main

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

piscis commented

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

Owner

Closes #32
Closes #35

Summary

README "Claude Code setup" now matches this repo's .mcp.json. The one exception is the vicoli-specific FORGEJO_URL default, which is left out on purpose so that public Consumers don't silently point at code.vicoli.de.

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

The claude mcp add line gets the same flag.

Added prose:

Prerequisites: Docker and a Forgejo personal access token
Why --pull=always: with :3, each session start picks up new minor and patch releases and Rebuilds
Export both FORGEJO_URL and FORGEJO_ACCESS_TOKEN. If your token is stored under another name, alias it with e.g. export FORGEJO_ACCESS_TOKEN=$FORGEJO_TOKEN
Token scopes are the only guardrail, because Upstream has no read-only mode or tool filtering
The same command/args work in any stdio MCP client
Forgejo on the Consumer's own machine: use host.docker.internal (on Linux, also add --add-host=host.docker.internal:host-gateway)

The one-off initialize check, HTTP mode and the Tags section are unchanged.

Deviation from #32: the ticket asked for the ${FORGEJO_URL:-https://code.vicoli.de} default and the "FORGEJO_URL now has a default" prose. The maintainer decided against both.

Evidence

Diff of the forgejo entry in .mcp.json against the README snippet:

<         "-e", "FORGEJO_URL=${FORGEJO_URL:-https://code.vicoli.de}",
>         "-e", "FORGEJO_URL",

The only other difference is the trailing comma after the entry, which comes from JSON context.

Merge Danger

Door: two-way

Blast Radius: docs

Consumers who copy the new snippet will pull on each session start.

Closes #32 Closes #35 ## Summary README "Claude Code setup" now matches this repo's `.mcp.json`. The one exception is the vicoli-specific `FORGEJO_URL` default, which is left out on purpose so that public Consumers don't silently point at code.vicoli.de. ```diff "args": [ - "run", "-i", "--rm", + "run", "-i", "--rm", "--pull=always", "-e", "FORGEJO_URL", "-e", "FORGEJO_ACCESS_TOKEN", "code.vicoli.de/vicoli-oss/forgejo-mcp:3" ] ``` The `claude mcp add` line gets the same flag. Added prose: - Prerequisites: Docker and a Forgejo personal access token - Why `--pull=always`: with `:3`, each session start picks up new minor and patch releases and Rebuilds - Export both `FORGEJO_URL` and `FORGEJO_ACCESS_TOKEN`. If your token is stored under another name, alias it with e.g. `export FORGEJO_ACCESS_TOKEN=$FORGEJO_TOKEN` - Token scopes are the only guardrail, because Upstream has no read-only mode or tool filtering - The same `command`/`args` work in any stdio MCP client - Forgejo on the Consumer's own machine: use `host.docker.internal` (on Linux, also add `--add-host=host.docker.internal:host-gateway`) The one-off `initialize` check, HTTP mode and the Tags section are unchanged. **Deviation from #32:** the ticket asked for the `${FORGEJO_URL:-https://code.vicoli.de}` default and the "FORGEJO_URL now has a default" prose. The maintainer decided against both. ## Evidence Diff of the `forgejo` entry in `.mcp.json` against the README snippet: ``` < "-e", "FORGEJO_URL=${FORGEJO_URL:-https://code.vicoli.de}", > "-e", "FORGEJO_URL", ``` The only other difference is the trailing comma after the entry, which comes from JSON context. ## Merge Danger **Door:** two-way **Blast Radius:** docs Consumers who copy the new snippet will pull on each session start.

piscis added 1 commit

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