fix: MCP migrator ignores servers using 'transport' field (VS Code extension format)

[OzMan21]

Problem

The VS Code extension writes MCP server configs with transport field (e.g., "transport": "sse"), but the CLI's mcp-migrator.ts only checks for the type field. This field name mismatch causes all SSE/HTTP transport servers to be silently skipped with:

WARN  service=kilocode.mcp-migrator name=cipher-direct local MCP server missing command, skipping

This means MCP servers configured via the VS Code extension UI are never loaded by the CLI.

Root Cause

In packages/opencode/src/kilocode/mcp-migrator.ts:

function isRemote(server: KilocodeMcpServer): boolean {
  return !!server.type && REMOTE_TYPES.has(server.type)
}

Only checks server.type, but the VS Code extension writes server.transport.

Fix

• Added getTransportType() helper that checks both type and transport fields (with type taking precedence)
• Updated isRemote() to use getTransportType()
• Added transport field to KilocodeMcpServer interface
• Added 6 regression tests

Config files affected

Any MCP config written by the VS Code extension UI uses transport instead of type, including:

• Global mcp_settings.json
• Project-level .kilocode/mcp.json

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (2 files)

• packages/opencode/src/kilocode/mcp-migrator.ts
• packages/opencode/test/kilocode/mcp-migrator.test.ts

---

_{Reviewed by gpt-5.4-20260305 · 436,857 tokens}