Ruben Cagnie
03/23/2026, 1:35 PMMCPToolRegistryProvider.fromClient is now failing for us, because our custom transport isn't one of the 2 provided. Here's the code that throws this exception
Could this be updated - so custom transports can be used? Or would that break other functionality?Vadim Briliantov
03/23/2026, 10:47 PMnull value:
McpMetadataKeys.McpTransportType to when (mcpClient.transport) {
is SseClientTransport -> McpTransportType.Tcp
is StdioClientTransport -> McpTransportType.Stdio
else -> error("Unexpected null for client transport: ${mcpClient.transport}")
}.value,
But we have to check with folks who added this lines for OTel — that it wouldn’t break their OTel client.
In the meantime, feel free to just copy-paste McpToolRegistryProvider.fromClient and write your own logic there (just remove that error esentially). It’s just ~20 lines of code.Ruben Cagnie
03/23/2026, 10:48 PMRuben Cagnie
03/23/2026, 10:48 PMRuben Cagnie
03/23/2026, 10:49 PMVadim Briliantov
03/23/2026, 10:49 PMnull. Hope he responds tomorrow — and then we can update it 🙂Ruben Cagnie
03/23/2026, 10:51 PMVadim Briliantov
03/25/2026, 12:38 AMRuben Cagnie
03/25/2026, 1:39 AMRuben Cagnie
03/25/2026, 1:40 AMVadim Briliantov
03/25/2026, 2:16 AMVadim Briliantov
03/25/2026, 2:22 AM