pal-e-docs

TODO: forgejo-mcp — Add set_label and comment_on_issue tools

todo-forgejo-mcp-label-comment-tools Todo

todo done
Project

What

The forgejo-mcp server is missing two tools that agents need for the sprint workflow:
  • set_label — add/replace a label on a Forgejo issue. Currently agents can't set labels without Bash + curl.
  • comment_on_issue — comment on a Forgejo issue (not a PR). Currently only comment_on_pr exists. QA can't comment on issues at all since QA has no Bash access.

Why

Sprint workflow automation (plan-2026-03-03-sprint-workflow-automation) uses Forgejo labels as the DORA instrumentation layer. Currently, label-setting is enforced by PostToolUse hooks using curl. This works but is a workaround — proper MCP tools would let agents set labels and comment on issues directly, enabling cleaner skill definitions and removing the hook-as-workaround pattern.

Workaround (current)

PostToolUse hooks in forgejo-helper.sh use curl to set labels and comment on issues. This works because hooks run as shell scripts with full API access. But it means the logic lives in hooks instead of in agent workflows where it belongs.

Repo

forgejo_admin/forgejo-mcp
  • plan-2026-03-03-sprint-workflow-automation Phase 3 — discovered the gap
  • agent-workflow — label signaling protocol