@olaservo I see you added the waiting for submitter tag - is there something else to do on my end? I thought I addressed your comment, lmk if there’s anything else you want from me :)

Hi @antholeole , I'm good to merge this but for some reason some new formatting issues are showing up in the CI checks - could you resolve that? (If I make those changes it won't count my approval.) Thanks!

Sgtm, will fix this tomorrow, thanks for taking another look.

Hello,

This seem to lead to an issue discussed in #699, especially the code in useConnection

https://github.com/modelcontextprotocol/inspector/pull/611/files#diff-1308b8974395372ca4d89e566b653312adcb1a690a926bb21431639928db2701R566-R569

Please check?

And here is what happens:

whenever logging/setLevel is called, the MCP server has no default handler for this request, therefore it goes into the "Method not found" flow.

To resolve it, the MCP server has to register a requestHandler for this method, however I would consider this worth reverting until a more graceful way to handle this is implemented.

Temporary workarounds (if server in your control)

• Disable the "logging" capabilities of your server
• If you wish to leave them enabled, add a requestHandler to your server like so

server.setRequestHandler(SetLevelRequestSchema, request => {
                        console.log(`--- Logging level: ${request.params.level}`);
                        return {};
                    });