Skip to content

feat: auto-configure Claude Desktop on first Smart Bridge run - #12

Merged
thomhoffer-arch merged 2 commits into
mainfrom
claude/review-claude-bridge-BPfhX
Apr 13, 2026
Merged

feat: auto-configure Claude Desktop on first Smart Bridge run#12
thomhoffer-arch merged 2 commits into
mainfrom
claude/review-claude-bridge-BPfhX

Conversation

@thomhoffer-arch

Copy link
Copy Markdown
Collaborator

No description provided.

claude added 2 commits April 13, 2026 10:29
- Add esbuild + zip step to release.yml that produces clashcontrol-mcp.mcpb
- Upload .mcpb alongside platform binaries in GitHub Releases
- Fix manifest.json entry_point to server/index.js (matches .mcpb internal layout)

Now every merged PR automatically produces the .mcpb file —
BIM managers download it from Releases and double-click to install.
Zero manual steps for ClashControl, zero terminal for end users.

Verified locally: esbuild bundles to 1.4MB, zips to 214KB .mcpb
containing manifest.json + server/index.js.

https://claude.ai/code/session_01XEvUykWcLc452uxGWPb1mb
When the Smart Bridge binary starts, it now automatically adds itself
to Claude Desktop's claude_desktop_config.json if not already present.
Points to the installed binary path with --mcp flag.

This means the full setup flow is now:
1. User downloads and runs the Smart Bridge binary
2. Binary self-installs to a permanent location (existing)
3. Binary configures Claude Desktop automatically (NEW)
4. User restarts Claude Desktop — ClashControl tools appear

No manual JSON editing, no terminal, no .mcpb download needed.
Preserves any existing mcpServers entries in the config.

https://claude.ai/code/session_01XEvUykWcLc452uxGWPb1mb
@thomhoffer-arch
thomhoffer-arch merged commit 4d5edad into main Apr 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants