feat: add Gitea issue comment list/create MCP tools (#126) #127
No Reviewers
Labels
Clear labels
allocator
anti-stomp
architecture
bug
chore
codex
concurrency
contamination
control-plane
dashboard
database
design
documentation
enhancement
gitea
glitchtip
important
incident
incident-bridge
integration
jenkins
labels
leases
mcp
mcp-health
mcp-menu
multi-project
mutating
nice-to-have
observability
portability
preflight
protected-branch
queue
read-only
reconnect
recovery
refactor
release
reliability
resumable-review
reviewer
roadmap
safety
security
self-hosted
sentry
stale-runtime
status:blocked
status:in-progress
status:pr-open
status:ready
terminal-lock
testing
tracker
type:bug
type:feature
type:feature
type:guardrail
visibility
workflow
workflow-hardening
workflow-hardening
Controller-owned work allocator
Prevent concurrent LLM session stomping
Architecture / structural design
OpenAI Codex client / workflow session surface
Concurrent session safety
Workflow or session contamination incident
MCP control-plane coordination and allocation authority
MCP operational dashboard/queue view
Internal coordination storage (SQLite/Postgres)
Design / investigation, no implementation
Docs / runbooks
New feature or improvement
Gitea MCP workflow
GlitchTip integration
Operational or process incident requiring durable audit trail
Sentry-to-Gitea incident bridging
Integration testing
Jenkins integration
Label taxonomy management
Lease adopt/release/expire lifecycle
MCP server / tooling
MCP namespace and runtime health
MCP menu surface
Work spanning multiple monitoring projects or Gitea repos
Mutating action; requires gating
Observability, metrics, traces, error reporting
Cross-platform / portability
Shared preflight gates before mutation
Protected branch / stable-branch policy concern
Work queue visibility and allocation
Read-only, no mutation
MCP client reconnect/reload recovery path
Recovery paths for stale/foreign leases
Code refactor / restructure
Release / versioning
Reliability / failure handling
Persist and resume prepared review verdicts across sessions
Reviewer workflow tooling
Roadmap / umbrella issue
Safety rails and fail-closed mutation guards
Security / trust boundary
Self-hosted infrastructure integration
Sentry error monitoring integration
Stale backend daemon / runtime-vs-master parity failures
Issue is blocked
Issue is being worked on
Issue has an open pull request
Issue is ready for work
Terminal review lock (#332) path
Tests / test coverage
Issue tracker hygiene / meta
Bug or defect
Feature or enhancement
Feature or enhancement
Safety gate or guardrail
Workflow state visibility for LLMs/operators
Cross-tool workflow
LLM workflow coordination hardening
LLM workflow coordination hardening
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Scaled-Tech-Consulting/Gitea-Tools#127
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Implements #126: first-class MCP tools for Gitea issue discussion comments, closing the gap where operators had to fall back to direct API scripts (as happened for mcp-control-plane #24).
New tools
gitea_list_issue_comments(issue_number, limit, remote, host, org, repo)— lists an issue's discussion comments. Returns commentid,author,created_at,updated_at,body. Gated ongitea.read(fail closed, no API call when blocked).gitea_create_issue_comment(issue_number, body, remote, host, org, repo)— posts a markdown comment to the issue thread. Returnscomment_id+issue_number. Gated ongitea.issue.comment— separately from thegitea.pr.*review/merge family; a profile holding full PR review permissions cannot post issue comments and vice versa. Empty body blocked. Audit-logged ascreate_issue_commentwhenGITEA_AUDIT_LOGis configured.Safety
/pulls/{n}/reviews— endpoint separation is tested.GITEA_MCP_REVEAL_ENDPOINTS=1admin opt-in (consistent with #120; forward-compatible with #125)._redactbefore being raised.issue_numberrequired; repo targeting uses only the standard remote/org/repo arguments.Tests
TestIssueCommentTools— 14 new tests: list/create success, output redaction by default, reveal opt-in, permission blocks (missing read, PR-review-perms-don't-grant-issue-comments, forbidden-overrides-allowed), empty body, missing issue with redacted error, review-endpoint separation, unknown remote.Full suite: 481 passed, 6 skipped.
git diff --checkclean;py_compileclean.Docs
New section "Issue comments versus PR reviews (#126)" in
docs/gitea-execution-profiles.md.Follow-up for operator
The live
prgs-authorprofile does not currently allowgitea.issue.comment, so the create tool will fail closed until the operator adds that operation to the intended profiles in the live config (config change is operator-owned; not part of this PR).Closes #126
Independent review of PR #127 at pinned head
5aeb51f132.Validation performed in a clean detached review worktree:
Manual review notes:
Verdict: approve.