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

Merged

jmiller merged 1 commits from feat/33-rename-mokogitea-tools into main 2026-07-06 03:01:13 +00:00

Conversation 1 Commits 1 Files Changed 4

+188 -118

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

Owner

Copy Link

Copy Source

Summary

Implements #33 (Gitea -> MokoGitea brand normalization for the MCP tool surface).

Part 1 - rename gitea_* -> mokogitea_* with backward-compatible aliases

• Added a single registerTool() wrapper (near server creation) that derives the canonical mokogitea_* name from each gitea_* literal and registers it, then also registers the legacy gitea_* name as a deprecated alias pointing at the same handler.
• Mechanically replaced all 111 server.tool(...) definition call sites with registerTool(...); a grep confirms zero server.tool( definition calls remain outside the wrapper.
• Legacy aliases are env-gated: enabled by default, disabled by setting MOKOGITEA_MCP_LEGACY_ALIASES to a falsy value (0/false/off/no).
• Server version bumped to 1.5.0; README updated (canonical vs deprecated naming section, intro/counts, example).

Tradeoff: while aliases are enabled, dual-registration roughly doubles the exposed tool count (~222) during the deprecation window. Disabling the env var returns to the 111 canonical names.

Wrapper typing note: an initial ...rest: [string, any, any] signature compiled the wrapper but erased zod-schema -> handler-arg inference at every call site (noImplicitAny errors on handler params). Resolved by making registerTool generic to mirror the SDK's typed overload: registerTool<Args extends ZodRawShapeCompat>(name, description, paramsSchema: Args, cb: ToolCallback<Args>), importing ToolCallback and ZodRawShapeCompat from the MCP SDK. Full inference preserved; npm run build is clean.

Part 2 - metadata fields + brand fix

• display_name: not added as a settable param. The fork's RepoMetadata has no display_name column; it is derived server-side (DerivedDisplayName() from extension_type + name). Added a code comment documenting this so it isn't re-added as a silent no-op.
• Brand fix: standards_version description changed from mokoplatform standards version -> mokocli standards version. No other mokoplatform/moko-platform strings remain in src/ or README.
• Confirmed metadata tools hit /repos/{owner}/{repo}/metadata; no /manifest references remain anywhere in the MCP.

Build / housekeeping

• npm run build (tsc) succeeds with no errors.
• package.json 1.4.2 -> 1.5.0; CHANGELOG updated.

Closes #33

Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

## Summary Implements #33 (Gitea -> MokoGitea brand normalization for the MCP tool surface). ### Part 1 - rename `gitea_*` -> `mokogitea_*` with backward-compatible aliases - Added a single `registerTool()` wrapper (near server creation) that derives the canonical `mokogitea_*` name from each `gitea_*` literal and registers it, then also registers the legacy `gitea_*` name as a **deprecated alias** pointing at the same handler. - Mechanically replaced all **111** `server.tool(...)` definition call sites with `registerTool(...)`; a grep confirms **zero** `server.tool(` definition calls remain outside the wrapper. - Legacy aliases are **env-gated**: enabled by default, disabled by setting `MOKOGITEA_MCP_LEGACY_ALIASES` to a falsy value (`0`/`false`/`off`/`no`). - Server version bumped to 1.5.0; README updated (canonical vs deprecated naming section, intro/counts, example). **Tradeoff:** while aliases are enabled, dual-registration roughly doubles the exposed tool count (~222) during the deprecation window. Disabling the env var returns to the 111 canonical names. **Wrapper typing note:** an initial `...rest: [string, any, any]` signature compiled the wrapper but erased zod-schema -> handler-arg inference at every call site (noImplicitAny errors on handler params). Resolved by making `registerTool` generic to mirror the SDK's typed overload: `registerTool<Args extends ZodRawShapeCompat>(name, description, paramsSchema: Args, cb: ToolCallback<Args>)`, importing `ToolCallback` and `ZodRawShapeCompat` from the MCP SDK. Full inference preserved; `npm run build` is clean. ### Part 2 - metadata fields + brand fix - `display_name`: **not** added as a settable param. The fork's `RepoMetadata` has no `display_name` column; it is derived server-side (`DerivedDisplayName()` from `extension_type` + `name`). Added a code comment documenting this so it isn't re-added as a silent no-op. - Brand fix: `standards_version` description changed from `mokoplatform standards version` -> `mokocli standards version`. No other `mokoplatform`/`moko-platform` strings remain in `src/` or README. - Confirmed metadata tools hit `/repos/{owner}/{repo}/metadata`; **no** `/manifest` references remain anywhere in the MCP. ### Build / housekeeping - `npm run build` (tsc) succeeds with no errors. - `package.json` 1.4.2 -> 1.5.0; CHANGELOG updated. Closes #33 Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

jmiller added 1 commit 2026-07-06 02:46:26 +00:00

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

Part 1: Introduce a single registerTool() wrapper that registers each tool
under its canonical mokogitea_* name and, when enabled, the legacy gitea_*
name as a deprecated alias pointing at the same handler. Legacy aliases are
on by default and can be disabled via MOKOGITEA_MCP_LEGACY_ALIASES (falsy).
All 111 server.tool(...) call sites now use registerTool(...). Server version
bumped to 1.5.0; README documents canonical vs deprecated naming.

Part 2: metadata brand fix -- standards_version description now says
"mokocli standards version" (was "mokoplatform"). Added a comment noting
display_name is server-derived (no settable param). No /manifest references
remain.

Closes #33

Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

jmiller commented 2026-07-06 02:46:41 +00:00

Author

Owner

Copy Link

Copy Source

Wiki reminder: docs are wiki-first -- if this PR changes behavior, usage, config, or standards, please update the repo wiki before/after merge. (non-blocking)

<!-- wiki-reminder --> **Wiki reminder:** docs are wiki-first -- if this PR changes behavior, usage, config, or standards, please update the repo wiki before/after merge. _(non-blocking)_

jmiller merged commit 48af706189 into main 2026-07-06 03:01:13 +00:00

jmiller deleted branch feat/33-rename-mokogitea-tools 2026-07-06 03:01:15 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

breaking-change

Breaking API or behavior change

ci-cd

CI/CD pipeline changes

config

Configuration changes

dependencies

Dependency updates

deploy-failure

Deployment failed

docker

Docker/container changes

documentation

Documentation changes

good first issue

Good for newcomers

health-check

Repo health check result

help wanted

Extra attention needed

javascript

JavaScript code

mokostandards

Related to MokoStandards framework

push-failure

Git push operation failed

security

Security vulnerability or hardening

size/l

200-500 lines changed

size/m

50-200 lines changed

size/s

10-50 lines changed

size/xl

500+ lines changed

size/xs

< 10 lines changed

standards-drift

Deviates from MokoStandards

standards-update

MokoStandards compliance update

sync-failure

Sync or mirror failed

typescript

TypeScript code

work-in-progress

Draft or incomplete work

bug

Something is not working

duplicate

This issue or pull request already exists

enhancement

New feature

help wanted

Need some help

invalid

Something is wrong

question

More information is needed

wontfix

This won't be fixed

No labels

Priority -

Type -

Milestone

No items

No Milestone

Assignees

Clear assignees

jmiller (Jonathan Miller)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/mcp-mokogitea-api#34