Rename MCP tools gitea_* → mokogitea_* (brand alignment) + add manifest metadata fields #33

New Issue

2026-07-06T00:42:02Z

jmiller commented

2026-07-06 00:42:02 +00:00

Rename tool prefix `gitea_` → `mokogitea_`

All tools this MCP server exposes are prefixed gitea_ (e.g. gitea_repo_get, gitea_pull_merge, gitea_manifest_update, gitea_api_request, gitea_issue_create, …). Per the org-wide Gitea→MokoGitea brand normalization, rename the tool names to mokogitea_* (e.g. mokogitea_repo_get).

Keep backward-compatible aliases for the old gitea_* names for a deprecation window if feasible (avoid breaking existing agent configs/skills that call gitea_*), then remove.
Update the server name/description and any docs/README accordingly.
Note the connection var names (vars.GITEA_URL/GITEA_ORG, secrets.*_TOKEN) are a separate concern — this issue is about the tool names.

Also: `gitea_manifest_update` is missing first-class metadata fields

The manifest metadata now includes element_name, extension_type, and display_name (first-class fields the fork uses to generate the Joomla updates.xml feed — .mokogitea/manifest.xml is deprecated). But gitea_manifest_update's schema only exposes name/org/description/version/license/platform/package_type/entry_point/language/standards_*. To set element_name/extension_type/display_name I had to fall back to a raw PUT /repos/{owner}/{repo}/manifest.

Please add element_name, extension_type, display_name (and any other first-class manifest fields — maintainer, maintainer_url, info_url, target_version, php_minimum, version_prefix) to the (moko)gitea_manifest_update tool schema so the feed-driving fields are settable directly. Context: getting these right is what fixes client Joomla update feeds (see MokoGitea-Fork#752).

## Rename tool prefix `gitea_*` → `mokogitea_*` All tools this MCP server exposes are prefixed `gitea_` (e.g. `gitea_repo_get`, `gitea_pull_merge`, `gitea_manifest_update`, `gitea_api_request`, `gitea_issue_create`, …). Per the org-wide Gitea→MokoGitea brand normalization, rename the tool names to `mokogitea_*` (e.g. `mokogitea_repo_get`). - Keep backward-compatible aliases for the old `gitea_*` names for a deprecation window if feasible (avoid breaking existing agent configs/skills that call `gitea_*`), then remove. - Update the server name/description and any docs/README accordingly. - Note the connection var names (`vars.GITEA_URL`/`GITEA_ORG`, `secrets.*_TOKEN`) are a separate concern — this issue is about the **tool names**. ## Also: `gitea_manifest_update` is missing first-class metadata fields The manifest metadata now includes **`element_name`**, **`extension_type`**, and **`display_name`** (first-class fields the fork uses to generate the Joomla `updates.xml` feed — `.mokogitea/manifest.xml` is deprecated). But `gitea_manifest_update`'s schema only exposes name/org/description/version/license/platform/package_type/entry_point/language/standards_*. To set `element_name`/`extension_type`/`display_name` I had to fall back to a raw `PUT /repos/{owner}/{repo}/manifest`. Please add `element_name`, `extension_type`, `display_name` (and any other first-class manifest fields — `maintainer`, `maintainer_url`, `info_url`, `target_version`, `php_minimum`, `version_prefix`) to the `(moko)gitea_manifest_update` tool schema so the feed-driving fields are settable directly. Context: getting these right is what fixes client Joomla update feeds (see MokoGitea-Fork#752).

jmiller commented

2026-07-06 00:42:07 +00:00

Branch created: feature/33-rename-mcp-tools-gitea-mokogitea-brand-a

git fetch origin
git checkout feature/33-rename-mcp-tools-gitea-mokogitea-brand-a

Branch created: [`feature/33-rename-mcp-tools-gitea-mokogitea-brand-a`](https://git.mokoconsulting.tech/MokoConsulting/mcp-mokogitea-api/src/branch/feature/33-rename-mcp-tools-gitea-mokogitea-brand-a) ```bash git fetch origin git checkout feature/33-rename-mcp-tools-gitea-mokogitea-brand-a ```

jmiller referenced this issue from a commit

2026-07-06 02:44:57 +00:00

feat(tools): rename gitea_* -> mokogitea_* with deprecated aliases; metadata brand fix (#33)

jmiller referenced a pull request that will close this issue

2026-07-06 02:46:25 +00:00

feat(tools): rename gitea_* -> mokogitea_* with deprecated aliases; metadata brand fix (#33) #34

jmiller closed this issue

2026-07-06 03:01:14 +00:00

jmiller referenced this issue from a commit

2026-07-06 03:01:14 +00:00

Merge pull request 'feat(tools): rename gitea_* -> mokogitea_* with deprecated aliases; metadata brand fix (#33)' (#34) from feat/33-rename-mokogitea-tools into main

Sign in to join this conversation.