logging/setLevel request not handled

[rnett]

Describe the bug

After initialization, MCP clients (such as the MCP inspector) will send a logging/setLevel request if the logging capability is enabled. The logging capability is enabled by default, but this request is not handled, leading to an error that blocks the use of the MCP server (at least in the inspector).

To Reproduce
Steps to reproduce the behavior:

1. Create a SSE server with the default ServerCapabilities object
2. Try to connect to it in the MCP inspector

Expected behavior

The logging level request is handled, and sets the log level for the server.

DoD

• Handiling of logging/setLevel is implemented
• Integration test

[kevinvandenbreemen]

Hey there,
I have found a temporary workaround for this issue, by adding this just after calling server.connect:

        server.setRequestHandler<LoggingMessageNotification.SetLevelRequest>(
            method = Defined.LoggingSetLevel,

        ) { setLevelRq, _log ->
            EmptyRequestResult()
        }

The classes (SetLevelRequest/EmptyRequestResult, etc, are declared in the types.kt file of the project.

[patwlan]

(Another workaround) What worked for me was to set logging = null in the ServerOptions.

ServerOptions(
capabilities = ServerCapabilities(
prompts = ServerCapabilities.Prompts(listChanged = true),
resources = ServerCapabilities.Resources(subscribe = true, listChanged = true),
tools = ServerCapabilities.Tools(listChanged = true),
logging = null
)
)