Consolidate local MCP installs under ~/mcp/ #1

New issue

Closed

opened 2026-04-20 13:45:42 +00:00 by claude-bot · 1 comment

claude-bot commented

2026-04-20 13:45:42 +00:00

Collaborator

Context

As of 2026-04-20, locally-installed MCP servers are scattered across the home directory with no consistent convention:

Forgejo: ~/go/bin/forgejo-mcp.exe (Go binary, installed via go install)
PowerAutomate: ~/AppData/Local/powerautomate-mcp/ (Windows installer path)
protonmail-pro-mcp: ~/mcp/protonmail-pro-mcp/ (established 2026-04-20 as the forward-looking convention)
npx-based (novamira-*, Gmail, Drive): no local dir, remote or ephemeral

Going forward, all new local MCPs will live under ~/mcp/<name>/. This issue covers back-migrating the existing two.

What needs to be done

Move ~/go/bin/forgejo-mcp.exe → ~/mcp/forgejo/forgejo-mcp.exe
Update the claude mcp registration to point at the new path
Document a rebuild-and-copy plan so future go install ...@latest runs don't drift back to ~/go/bin/ unnoticed (options: symlink ~/mcp/forgejo/forgejo-mcp.exe → ~/go/bin/forgejo-mcp.exe, or a tiny wrapper script under ~/mcp/forgejo/ that shells out to the Go-installed binary)
Decide whether PowerAutomate's install is Windows-managed (don't move — breaks updater) or manual (safe to move). If manual, relocate to ~/mcp/powerautomate/ and update registration.
Verify all MCPs still connect via claude mcp list after the move.

Why not do it now

The Minerva protonmail-pro-mcp install prompted the convention but doing the reorg in the same session would violate surgical-changes — it's a cosmetic reorganization of working infrastructure, best batched into a dedicated housekeeping pass rather than slipped into a feature install.

Risks

Forgejo: go install ...@latest recreates the binary at ~/go/bin/ — any version update silently reverts the move unless step 3 is done.
PowerAutomate: Windows-managed installs often hardcode their path; moving may break future updates.
Both MCPs must be re-registered after the move or they'll 404 at next session start.

Definition of done

ls ~/mcp/ shows one directory per locally-installed MCP.
claude mcp list shows all MCPs still ✓ Connected.
A short README under ~/mcp/ documents the convention for the next "where do I put this MCP" question.

## Context As of 2026-04-20, locally-installed MCP servers are scattered across the home directory with no consistent convention: - **Forgejo**: `~/go/bin/forgejo-mcp.exe` (Go binary, installed via `go install`) - **PowerAutomate**: `~/AppData/Local/powerautomate-mcp/` (Windows installer path) - **protonmail-pro-mcp**: `~/mcp/protonmail-pro-mcp/` (established 2026-04-20 as the forward-looking convention) - **npx-based** (novamira-*, Gmail, Drive): no local dir, remote or ephemeral Going forward, all **new** local MCPs will live under `~/mcp/<name>/`. This issue covers back-migrating the existing two. ## What needs to be done 1. Move `~/go/bin/forgejo-mcp.exe` → `~/mcp/forgejo/forgejo-mcp.exe` 2. Update the `claude mcp` registration to point at the new path 3. Document a rebuild-and-copy plan so future `go install ...@latest` runs don't drift back to `~/go/bin/` unnoticed (options: symlink `~/mcp/forgejo/forgejo-mcp.exe` → `~/go/bin/forgejo-mcp.exe`, or a tiny wrapper script under `~/mcp/forgejo/` that shells out to the Go-installed binary) 4. Decide whether PowerAutomate's install is Windows-managed (don't move — breaks updater) or manual (safe to move). If manual, relocate to `~/mcp/powerautomate/` and update registration. 5. Verify all MCPs still connect via `claude mcp list` after the move. ## Why not do it now The Minerva protonmail-pro-mcp install prompted the convention but doing the reorg in the same session would violate surgical-changes — it's a cosmetic reorganization of working infrastructure, best batched into a dedicated housekeeping pass rather than slipped into a feature install. ## Risks - **Forgejo**: `go install ...@latest` recreates the binary at `~/go/bin/` — any version update silently reverts the move unless step 3 is done. - **PowerAutomate**: Windows-managed installs often hardcode their path; moving may break future updates. - Both MCPs must be re-registered after the move or they'll 404 at next session start. ## Definition of done - `ls ~/mcp/` shows one directory per locally-installed MCP. - `claude mcp list` shows all MCPs still ✓ Connected. - A short README under `~/mcp/` documents the convention for the next "where do I put this MCP" question.

claude-bot added the

area/tooling

label

2026-04-20 14:02:56 +00:00

claude-bot commented

2026-07-22 05:40:03 +00:00

Author

Collaborator

Migrated under Portfolio decision D-0027 to mike/portfolio#2. The destination preserves the original risks and acceptance criteria but requires a fresh inventory before any path changes, because the 2026-04-20 install list is historical.

Migrated under Portfolio decision D-0027 to [mike/portfolio#2](https://code.rinaldifamily.org/mike/portfolio/issues/2). The destination preserves the original risks and acceptance criteria but requires a fresh inventory before any path changes, because the 2026-04-20 install list is historical.

claude-bot closed this issue

2026-07-22 05:40:07 +00:00