You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(#47): interactive MCP name conflict resolution during apc collect
When multiple tools provide an MCP server with the same name, apc collect
now detects the collision and prompts the user:
⚠ MCP server name conflict: 'my-mcp'
# Source Tool Command Args
1 claude-code npx ...
2 cursor node ...
Keep which as 'my-mcp'? [1-2]: 1
Entry from 'cursor': [r]ename to 'my-mcp-cursor' or [d]iscard? r
- overwrite (discard): one canonical entry kept, other dropped
- rename: non-canonical entry kept as '<name>-<source_tool>'
- --yes: skips prompts, passes all entries through (merge handles dedup)
Tests (21):
- no-conflict cases: empty, single, different names, same tool
- --yes mode: two-way, three-way, mixed conflict+clean
- interactive overwrite: keep chosen, discard other, clean servers
always present, invalid choice fallback, discard confirmation
- interactive rename: suffix added, data preserved, canonical unchanged,
three-way rename-all, three-way rename+discard, result counts
- CLI integration: collect --yes with shared name, no prompt when clean
0 commit comments