Kilo Code v7.0.33+ moved MCP config out of the VS Code extension's
globalStorage/mcp_settings.json to a CLI-style kilo.jsonc under ~/.config/kilo,
with a new schema (https://app.kilo.ai/config.json): an "mcp" container,
type:"remote" for HTTP servers (type:"local" for stdio), and an "enabled" flag.
Writing the legacy mcpServers / type:"http" / disabled config left the server
showing as stdio + disabled.
- KiloCodeConfigurator targets ~/.config/kilo/kilo.jsonc on every OS and declares
the new format (mcp container, type:remote/local, enabled:true, $schema)
- Generalize the per-client HTTP "type" override: replace the UsesStreamableHttpType
bool with McpClient.HttpTypeValue (Cline/Roo => "streamableHttp", Kilo => "remote",
default "http"); add StdioTypeValue, ServerContainerKey and SchemaUrl fields
- ConfigJsonBuilder honors ServerContainerKey ("mcp") and writes a root $schema;
JsonFileMcpConfigurator.CheckStatus/Unregister read/remove from the configured
container so status detection and teardown work for Kilo
- Replace StreamableHttpTypeTests with ClientConfigFormatTests covering Kilo's
remote/mcp/enabled format, Cline's streamableHttp, and generic http
Verified: 5 new tests + 13 existing config tests pass (EditMode, Unity 2021.3).
Shutong Wu
afa447ef38