set loggingConsumer after client initialization

Expected Behavior

We should be able to set a loggingConsumer on McpClient after querying its capabilities.

var capabilities = client.getServerCapabilities();
if (capabilities.logging() != null) {
    client.setLoggingLevel(McpSchema.LoggingLevel.INFO);
    client.setLoggingConsumer(consumer);
}

Current Behavior

Currently, we can set a loggingConsumer with McpClientTransport before client initialization. For example,

McpClient.sync(server.transport())
                .loggingConsumer(consumer)
                .build();

Context

However, many MCP servers' logging capabilities are not enabled. But we cannot query if the server has this capability before client initialization. Such a poor design makes it impossible to register a logging consumer safely.

Commencez par lire l’initialisation de McpClient et le flux d’interrogation des capacités, puis comparez-les à la configuration de loggingConsumer de McpClientTransport. Vérifiez le comportement de setLoggingLevel et setLoggingConsumer avant l’initialisation. C’est terminé lorsqu’un consumer peut être enregistré après que getServerCapabilities() a confirmé la prise en charge de la journalisation, sans casser l’utilisation existante du builder avant l’initialisation.