Context
Surfaced 2026-05-14 by the PMF subagent. Belongs in synthpanel repo; tracked here.
The friction
synthpanel ships an MCP server (python -m synth_panel.mcp) but adopting it from inside an active Claude Code session requires hand-editing ~/.claude/settings.json to register the server, then restarting the harness. Friction is high enough that most users will fall back to the SDK and never try the MCP path again.
What to fix
Ship a synthpanel mcp install CLI subcommand that:
- Detects the active Claude config (settings.json location, IDE plugin config, etc.)
- Registers the synthpanel MCP server with the right command + args
- Prints "Restart Claude Code to pick up the new MCP server" or, if possible, signals the running harness to reload
- Has an
--uninstall mirror for removal
Where this belongs
DataViking-Tech/SynthPanel. Mirror + close here once synthpanel-side issue exists.
Context
Surfaced 2026-05-14 by the PMF subagent. Belongs in synthpanel repo; tracked here.
The friction
synthpanel ships an MCP server (
python -m synth_panel.mcp) but adopting it from inside an active Claude Code session requires hand-editing~/.claude/settings.jsonto register the server, then restarting the harness. Friction is high enough that most users will fall back to the SDK and never try the MCP path again.What to fix
Ship a
synthpanel mcp installCLI subcommand that:--uninstallmirror for removalWhere this belongs
DataViking-Tech/SynthPanel. Mirror + close here once synthpanel-side issue exists.