Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 5 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

feat: convert Gitea-Tools into an MCP server #7

New Issue
Closed
opened 2026-06-21 18:35:35 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-06-21 18:35:35 -05:00
Owner
Copy Link
Copy Source

Expose all script functionality as MCP tools via the official Python MCP SDK (FastMCP).

Tools:

  • gitea_create_issue — create an issue
  • gitea_create_pr — open a pull request
  • gitea_close_issue — close an issue
  • gitea_list_issues — query issues with filters
  • gitea_mark_issue — claim/release an issue
  • gitea_view_issue — inspect a single issue
  • gitea_mirror_refs — bidirectional ref sync

Benefits:

  • Solves macOS com.apple.provenance blocking (server is one long-lived process)
  • Structured JSON returns instead of stdout parsing
  • Any MCP-compatible agent can call the tools natively
  • Auth handled centrally by the server

Depends on: #1 (shared auth.py), #2 (list_issues), #5 (view_issue)

Expose all script functionality as MCP tools via the official Python MCP SDK (FastMCP). Tools: - `gitea_create_issue` — create an issue - `gitea_create_pr` — open a pull request - `gitea_close_issue` — close an issue - `gitea_list_issues` — query issues with filters - `gitea_mark_issue` — claim/release an issue - `gitea_view_issue` — inspect a single issue - `gitea_mirror_refs` — bidirectional ref sync Benefits: - Solves macOS com.apple.provenance blocking (server is one long-lived process) - Structured JSON returns instead of stdout parsing - Any MCP-compatible agent can call the tools natively - Auth handled centrally by the server Depends on: #1 (shared auth.py), #2 (list_issues), #5 (view_issue)
jcwalker3 added the important label 2026-06-21 18:35:40 -05:00
jcwalker3 added the status:in-progress label 2026-06-21 19:08:30 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
chore
documentation
Docs / runbooks
 gitea
Gitea MCP workflow
 important
mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
read-only
Read-only, no mutation
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
No Label important status:in-progress
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#7
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?