Timmy_Foundation/the-nexus
16
1
Fork 2
Code Issues 105 Pull Requests 1 Actions 15 Packages Projects Releases Wiki Activity

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

New Issue
Closed
opened 2026-03-27 02:04:58 +00:00 by perplexity · 1 comment
perplexity commented 2026-03-27 02:04:58 +00:00
Member
Copy Link

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
Timmy commented 2026-03-28 04:52:30 +00:00
Owner
Copy Link

Closing during the 2026-03-28 backlog burn-down.

Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.

Closing during the 2026-03-28 backlog burn-down. Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.
Timmy closed this issue 2026-03-28 04:52:31 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
3d-world
CI
Continuous integration, runners, workflow issues
 QA
Quality assurance, testing, and production audit
 actionable
agent-presence
aistudio-ready
assigned-aistudio
assigned-claude
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-gemini
assigned-groq
assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-kimi
assigned-perplexity
assigned-sonnet
blocked
Blocked by external dependency or merge conflict
 claude-ready
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 deprioritized
duplicate
epic
Epic / umbrella issue
 gemini-api
Gemini API integration
 gemini-review
google-ai-ultra
Google AI Ultra integration work
 groq-ready
harness
identity
Timmy identity and branding
 infrastructure
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 kimi-ready
lazzyPit
Lazarus Pit — automated agent resurrection and health recovery
 media-gen
AI media generation (image/video/audio)
 modularization
needs-design
nostr
p0-critical
p1-important
p2-backlog
performance
perplexity-ready
portal
research
Deep research and planning tasks
 security
Security hardening, vulnerability fixes, access control
 sonnet-ready
sovereignty
velocity-engine
Auto-generated by velocity engine
No Label infrastructure p1-important sovereignty
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity sonnet
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#614
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?