pal-e-docs

Bug: Forgejo MCP missing create_repo tool

bug-forgejo-mcp-missing-create-repo Todo

todo done
Project

Problem

The Forgejo MCP server (forgejo_admin/forgejo-mcp) has 12 tools but no create_repo tool. When a new repo is needed (e.g., creating pal-e-dora-exporter), agents must fall back to raw curl against the Forgejo API with hardcoded credentials. This breaks the MCP abstraction.
Current tools: create_issue, create_issue_and_branch, create_api_token, submit_pr, review_pr, comment_on_pr, merge_approved_pr, list_issues, list_prs, list_branches, get_repo, search_repos.

Root Cause

The create_repo endpoint (POST /api/v1/user/repos) was never implemented as an MCP tool in forgejo-mcp/src/forgejo_mcp/tools/workflows.py. The MCP was built around the PR lifecycle (issue -> branch -> code -> PR -> review -> merge) but missed the repo creation step that precedes that lifecycle.

Fix

Add a create_repo tool to forgejo-mcp/src/forgejo_mcp/tools/workflows.py that wraps POST /api/v1/user/repos with parameters:
  • name (required) -- repo name
  • description (optional)
  • auto_init (optional, default true) -- initialize with README
  • default_branch (optional, default "main")
  • private (optional, default false)
Possibly also add: delete_repo, fork_repo, update_repo (settings).

Impact

Every new service or project requires a Forgejo repo. Without this tool, agents cannot create repos autonomously -- they need raw API access with credentials that should be encapsulated by the MCP layer. This is a workflow gap, not a service outage.

Acceptance Criteria

  • [ ] create_repo tool available in Forgejo MCP
  • [ ] Can create a repo via MCP without needing raw API credentials
  • [ ] Tool returns repo URL and clone URL on success
  • plan-2026-03-01-dora-metrics-dashboard -- where the gap was discovered