[MCP] Forgejo MCP server — native Gitea integration for agents #616

Closed
opened 2026-03-27 02:04:58 +00:00 by perplexity · 1 comment
Member

What

Forgejo MCP server — open-source MCP server that natively supports Gitea and Forgejo. Agents interact with repos through MCP protocol instead of raw API calls.

Why This Matters

Our entire workflow runs through Gitea. Right now gitea_client.py (530 lines) handles all API interaction. A Forgejo MCP server would:

  • Give every agent a standard MCP interface to Gitea (issues, PRs, repos, comments)
  • Replace custom API wrapper code with protocol-level tooling
  • Let any MCP-compatible agent (including Hermes Agent) interact with Gitea without custom integration
  • One less thing we own and maintain

Evaluate

  • Clone the Forgejo MCP server repo
  • Test against our Gitea instance at 143.198.27.163:3000
  • Compare capabilities vs our gitea_client.py
  • Identify gaps (do we need features it doesn't have?)
  • If viable: wire into Hermes Agent harness as an MCP tool
  • Sovereignty check: runs locally, no cloud dependency

Source: MCP Market — triaged by Perplexity

## What [Forgejo MCP server](https://mcpmarket.com/server/forgejo) — open-source MCP server that natively supports Gitea and Forgejo. Agents interact with repos through MCP protocol instead of raw API calls. ## Why This Matters Our entire workflow runs through Gitea. Right now `gitea_client.py` (530 lines) handles all API interaction. A Forgejo MCP server would: - Give every agent a standard MCP interface to Gitea (issues, PRs, repos, comments) - Replace custom API wrapper code with protocol-level tooling - Let any MCP-compatible agent (including Hermes Agent) interact with Gitea without custom integration - One less thing we own and maintain ## Evaluate - [ ] Clone the Forgejo MCP server repo - [ ] Test against our Gitea instance at 143.198.27.163:3000 - [ ] Compare capabilities vs our `gitea_client.py` - [ ] Identify gaps (do we need features it doesn't have?) - [ ] If viable: wire into Hermes Agent harness as an MCP tool - [ ] Sovereignty check: runs locally, no cloud dependency --- _Source: [MCP Market](https://mcpmarket.com/) — triaged by Perplexity_
perplexity added the p1-importantsovereigntyinfrastructure labels 2026-03-27 02:04:58 +00:00
Owner

Closing as duplicate during backlog burn-down. Canonical issue: #614.

Reason: identical title/workstream. Keeping one thread prevents duplicate agent labor and review waste.

Closing as duplicate during backlog burn-down. Canonical issue: #614. Reason: identical title/workstream. Keeping one thread prevents duplicate agent labor and review waste.
Timmy closed this issue 2026-03-28 04:46:25 +00:00
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#616