Defame1297/holocron
0
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

gitea: wire real MCP server config into plugins/gitea/.mcp.json #66

New Issue
Closed
opened 2026-07-05 10:25:39 +00:00 by Claude · 2 comments
Claude commented 2026-07-05 10:25:39 +00:00
Collaborator
Copy Link

As part of the issue #6 gitea plugin redesign (deep-module skill split, see docs/adr/0011-gitea-skill-deep-modules.md for the full decision record), plugins/gitea/.mcp.json was deliberately left as an empty {"mcpServers": {}} shell. The actual gitea-mcp server configuration currently lives only in the user's ~/.claude.json, configured manually. This means the gitea plugin isn't installable/self-contained the way plugins/git/ and plugins/bin/ are (both declare their own MCP servers in their .mcp.json).

Wiring this in was explicitly deferred from issue #6 to keep that PR scoped to skill structure rather than plugin installation mechanics. This follow-up issue tracks doing that properly: server command/args, with token/URL sourced from env vars, not hardcoded — per this repo's credential-handling rules.

Follow-up from #6.

As part of the issue #6 gitea plugin redesign (deep-module skill split, see `docs/adr/0011-gitea-skill-deep-modules.md` for the full decision record), `plugins/gitea/.mcp.json` was deliberately left as an empty `{"mcpServers": {}}` shell. The actual gitea-mcp server configuration currently lives only in the user's `~/.claude.json`, configured manually. This means the `gitea` plugin isn't installable/self-contained the way `plugins/git/` and `plugins/bin/` are (both declare their own MCP servers in their `.mcp.json`). Wiring this in was explicitly deferred from issue #6 to keep that PR scoped to skill structure rather than plugin installation mechanics. This follow-up issue tracks doing that properly: server command/args, with token/URL sourced from env vars, not hardcoded — per this repo's credential-handling rules. Follow-up from #6.
Claude added the Kind/Enhancement
Priority
Medium
3
 labels 2026-07-05 10:25:39 +00:00
Defame1297 added this to the Tooling milestone 2026-08-10 19:11:36 +00:00
Claude commented 2026-09-09 19:53:08 +00:00
Author
Collaborator
Copy Link

Opened #132 implementing this — pinned gitea-mcp@v1.7.0, portable bare go command, GITEA_ACCESS_TOKEN/GITEA_HOST required via ${VAR} expansion with no inline defaults or hardcoded secrets. Full test suite and pre-push gate both green.

Opened #132 implementing this — pinned gitea-mcp@v1.7.0, portable bare `go` command, `GITEA_ACCESS_TOKEN`/`GITEA_HOST` required via `${VAR}` expansion with no inline defaults or hardcoded secrets. Full test suite and pre-push gate both green.
Claude commented 2026-09-16 15:12:52 +00:00
Author
Collaborator
Copy Link

The premise has changed on branch docs/simplification-audit (simplification audit finding 37, ADR-0024):

  • The target file is gone. Every plugin .mcp.json, plugins/gitea/.mcp.json included, was deleted along with native plugin install. Plugins are now consumed only through apm.
  • What's left to decide: if the gitea plugin should be self-contained, the MCP server has to be declared through apm's package manifest (plugins/gitea/apm.yml), with the token and URL taken from env vars. The other option is to decide the server stays user-configured in ~/.claude.json and close this issue.

Needs re-scoping before anyone works on it.

The premise has changed on branch `docs/simplification-audit` (simplification audit finding 37, ADR-0024): - **The target file is gone.** Every plugin `.mcp.json`, `plugins/gitea/.mcp.json` included, was deleted along with native plugin install. Plugins are now consumed only through apm. - **What's left to decide:** if the gitea plugin should be self-contained, the MCP server has to be declared through apm's package manifest (`plugins/gitea/apm.yml`), with the token and URL taken from env vars. The other option is to decide the server stays user-configured in `~/.claude.json` and close this issue. Needs re-scoping before anyone works on it.
Defame1297 added the
Reviewed
Won't Fix
3
 label 2026-09-21 20:05:26 +00:00
Sign in to join this conversation.
refactor/6-gitea-deep-modules
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label Kind/Enhancement
Priority
Medium
3
Reviewed
Won't Fix
3
Milestone
No items
No Milestone Tooling
Projects
Clear projects
No project
Assignees
Clear assignees
Claude renovate-bot Defame1297
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Defame1297/holocron#66
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?