Part of #408. Depends on daemon lifecycle.
Why
synthesizeMcpEntry() (bin/install-helpers.cjs) emits a stdio entry per provider. Daemon mode needs a single HTTP client entry instead.
What
When daemon mode is opted into, install writes one entry of the form:
{ "type": "http", "url": "http://127.0.0.1:<port>/mcp" }
instead of per-provider stdio entries.
Opt-in, not default. Consolidation changes tool names (mcp__claude-1__claude becomes mcp__unified-1__claude-1), which is breaking for anything referencing the old names. Landing that silently on ~1.2k downloads/month is not acceptable; default can flip in a later milestone once the path is proven.
Reuse findUnifiedMcpEntry() from #408's first fix so a user who already consolidated is recognised rather than re-slotted.
Acceptance
Part of #408. Depends on daemon lifecycle.
Why
synthesizeMcpEntry()(bin/install-helpers.cjs) emits a stdio entry per provider. Daemon mode needs a single HTTP client entry instead.What
When daemon mode is opted into, install writes one entry of the form:
{ "type": "http", "url": "http://127.0.0.1:<port>/mcp" }instead of per-provider stdio entries.
Opt-in, not default. Consolidation changes tool names (
mcp__claude-1__claudebecomesmcp__unified-1__claude-1), which is breaking for anything referencing the old names. Landing that silently on ~1.2k downloads/month is not acceptable; default can flip in a later milestone once the path is proven.Reuse
findUnifiedMcpEntry()from #408's first fix so a user who already consolidated is recognised rather than re-slotted.Acceptance
tool_prefixvalues resolve correctly under the HTTP entry (seeunifiedToolPrefix)