Skip to content

chore(mcp): install pal-mcp-server fork as a uv tool#224

Merged
laurigates merged 1 commit into
mainfrom
chore/pal-mcp-server-fork
Jun 3, 2026
Merged

chore(mcp): install pal-mcp-server fork as a uv tool#224
laurigates merged 1 commit into
mainfrom
chore/pal-mcp-server-fork

Conversation

@laurigates
Copy link
Copy Markdown
Owner

What

Switch the pal MCP server from uvx --from git+https://github.com/BeehiveInnovations/pal-mcp-server.git to the globally-installed pal-mcp-server command (laurigates/pal-mcp-server fork), and declare the install in the uv_tools registry.

Why

uvx --from git+... re-resolves the git source on every MCP launch, generating a process-spawn storm that taxes the macOS security stack (EndpointSecurity/XProtect inspect every spawn). Installing the fork once via uv tool install and invoking the bare command eliminates the per-launch git churn and picks up the fork's improvements.

Files

  • .mcp.json — repo-local project MCP config
  • .chezmoidata.toml[mcp_servers.pal] registry entry
  • .chezmoidata/uv_tools.tomlgit_tools install declaration

🤖 Generated with Claude Code

Replace the uvx-from-git launch of the pal MCP server with the globally-installed 'pal-mcp-server' command from the laurigates/pal-mcp-server fork.

- .mcp.json + .chezmoidata.toml mcp_servers registry: pal now runs the bare 'pal-mcp-server' command instead of 'uvx --from git+...BeehiveInnovations...'.
- .chezmoidata/uv_tools.toml: declare the fork in git_tools so run_onchange installs it via 'uv tool install' on apply.

Stops re-resolving the git source on every MCP launch (a process-spawn storm) and adopts the fork's improvements.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@laurigates laurigates self-assigned this Jun 2, 2026
@laurigates laurigates merged commit e83f1f9 into main Jun 3, 2026
8 checks passed
@laurigates laurigates deleted the chore/pal-mcp-server-fork branch June 3, 2026 06:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant