bug: manifest_update tool missing fields available in manifest API #649

New Issue

2026-06-19T07:18:54Z

jmiller commented

2026-06-19 07:18:54 +00:00

Description

The gitea_manifest_update MCP tool is missing several fields that the manifest API (PUT /repos/{owner}/{repo}/manifest) supports. This means these fields can only be set via raw API requests.

Missing fields

The following fields are returned by gitea_manifest_get and accepted by the raw PUT endpoint, but are not exposed as parameters in gitea_manifest_update:

display_name — human-readable extension name (e.g. "Package - MokoSuite CRM")
maintainer — maintainer name (e.g. "Moko Consulting")
maintainer_url — maintainer website URL
info_url — product info/support page URL
target_version — target Joomla version (e.g. "6..*")
php_minimum — minimum PHP version (e.g. "8.1")
element_name — Joomla element name (e.g. "pkg_mokosuitecrm")

Additional issue: `file_delete` tool broken

The gitea_file_delete tool returns "repository file already exists" errors — it appears to be calling a create endpoint instead of DELETE. Workaround was to use git clone + push.

Expected behavior

gitea_manifest_update should accept all fields that gitea_manifest_get returns, using merge semantics (only update fields that are provided, leave others unchanged).

Current workaround

Using gitea_api_request with PUT /repos/{owner}/{repo}/manifest directly, but this is a full replace — all fields must be sent or they get blanked out.

## Description The `gitea_manifest_update` MCP tool is missing several fields that the manifest API (`PUT /repos/{owner}/{repo}/manifest`) supports. This means these fields can only be set via raw API requests. ## Missing fields The following fields are returned by `gitea_manifest_get` and accepted by the raw `PUT` endpoint, but are **not exposed as parameters** in `gitea_manifest_update`: - `display_name` — human-readable extension name (e.g. "Package - MokoSuite CRM") - `maintainer` — maintainer name (e.g. "Moko Consulting") - `maintainer_url` — maintainer website URL - `info_url` — product info/support page URL - `target_version` — target Joomla version (e.g. "6..*") - `php_minimum` — minimum PHP version (e.g. "8.1") - `element_name` — Joomla element name (e.g. "pkg_mokosuitecrm") ## Additional issue: `file_delete` tool broken The `gitea_file_delete` tool returns `"repository file already exists"` errors — it appears to be calling a create endpoint instead of DELETE. Workaround was to use git clone + push. ## Expected behavior `gitea_manifest_update` should accept all fields that `gitea_manifest_get` returns, using merge semantics (only update fields that are provided, leave others unchanged). ## Current workaround Using `gitea_api_request` with `PUT /repos/{owner}/{repo}/manifest` directly, but this is a full replace — all fields must be sent or they get blanked out.

jmiller commented

2026-06-19 07:18:56 +00:00

Branch created: feature/649-bug-manifest-update-tool-missing-fields-

git fetch origin
git checkout feature/649-bug-manifest-update-tool-missing-fields-

Branch created: [`feature/649-bug-manifest-update-tool-missing-fields-`](https://code.mokoconsulting.tech/MokoConsulting/MokoGitea-Fork/src/branch/feature/649-bug-manifest-update-tool-missing-fields-) ```bash git fetch origin git checkout feature/649-bug-manifest-update-tool-missing-fields- ```

jmiller referenced this issue from MokoConsulting/mcp-mokogitea-api

2026-06-19 07:29:17 +00:00

fix: add missing fields to gitea_metadata_update tool (#649) #16

jmiller closed this issue

2026-06-20 20:02:18 +00:00

Sign in to join this conversation.