Describe the bug
By default, the UI has the log level set to debug. This doesn't send a "setLevel" message, and so a server implemented to spec will not emit logs.

As a workaround, I setLog to info or higher and then go back to debug to set the correct log level.

Expected behavior
On connection to the MCP server, a setLog level should be sent at debug to initiate logging.

Other Context

Its possible I'm misunderstanding the spec, but the waterfall diagram on the chart is pretty clear that a setLog message should come first