Write README: what the Image is, how to pull and configure it as an MCP server #18

New issue

Closed

opened 2026-09-30 14:16:16 +00:00 by piscis · 1 comment

piscis commented

2026-09-30 14:16:16 +00:00

Owner

README.md is empty. The repo is public (ADR 0004), so it's the first thing a Consumer sees.

It should cover at least:

What the Image is: a multi-arch container image of the Forgejo MCP server, built from a pinned Upstream Version (link to Upstream).
How to pull it anonymously: code.vicoli.de/vicoli-oss/forgejo-mcp, and the tag scheme (ADR 0003).
How to configure it as an MCP server in a client, with the required env vars (Forgejo URL, token).
Where the Pin lives (pin.env) and how Rebuilds work, for maintainers.

Split out while setting the org and repo descriptions on Forgejo.

`README.md` is empty. The repo is public (ADR 0004), so it's the first thing a Consumer sees. It should cover at least: - What the Image is: a multi-arch container image of the Forgejo MCP server, built from a pinned Upstream Version (link to Upstream). - How to pull it anonymously: `code.vicoli.de/vicoli-oss/forgejo-mcp`, and the tag scheme (ADR 0003). - How to configure it as an MCP server in a client, with the required env vars (Forgejo URL, token). - Where the Pin lives (`pin.env`) and how Rebuilds work, for maintainers. Split out while setting the org and repo descriptions on Forgejo.

piscis added the

needs-triage

label

2026-09-30 14:16:17 +00:00

piscis commented

2026-09-30 14:26:44 +00:00

Author

Owner

This was generated by AI during triage.

Closing as a duplicate of #9, which is already ready-for-agent and covers everything asked for here:

What the Image is and its link to Upstream → #9 "What this is"
Anonymous pull from code.vicoli.de/vicoli-oss/forgejo-mcp and the tag scheme (ADR 0003) → #9 "Quick start" and "Tags"
Setting it up as an MCP server with FORGEJO_URL / FORGEJO_ACCESS_TOKEN → #9 "Claude Code setup" (plus HTTP mode)
Where the Pin lives and how Rebuilds work → #9 "Tags" and "For maintainers". #9 now names pin.env explicitly.

The README work is tracked in #9, which is blocked by #7 so every snippet can be checked against the published Image.

> *This was generated by AI during triage.* Closing as a duplicate of #9, which is already `ready-for-agent` and covers everything asked for here: - What the Image is and its link to Upstream → #9 "What this is" - Anonymous pull from `code.vicoli.de/vicoli-oss/forgejo-mcp` and the tag scheme (ADR 0003) → #9 "Quick start" and "Tags" - Setting it up as an MCP server with `FORGEJO_URL` / `FORGEJO_ACCESS_TOKEN` → #9 "Claude Code setup" (plus HTTP mode) - Where the Pin lives and how Rebuilds work → #9 "Tags" and "For maintainers". #9 now names `pin.env` explicitly. The README work is tracked in #9, which is blocked by #7 so every snippet can be checked against the published Image.

piscis

2026-09-30 14:26:44 +00:00