Description

• In src/server/index.ts

  • In Server class
    • In constructor, when setting request handler for SetLevelRequestSchema
      • Remove check for transportSessionId when in condition wrapping call to _loggingLevels.set
      • Allows undefined sessionId to be a map key
    • Change _loggingLevels Map to allow string or undefined as a key.
      • Allows an STDIO server to have automatic log filtering if sendLoggingMessage is used.
    • In isMessageIgnored method
      • Made sessionId argument optional.
      • Will result in undefined for sessionless / STDIO servers
    • In sendLoggingMessage method,
      • Remove sessionId check from condition wrapping call to notification
      • Allows STDIO servers to have automatic log filtering

• In src/server/index.test.ts

  • Added tests
    • "should respect log level for transport without sessionId"
    • "should respect log level for transport with sessionId"

Motivation and Context

While refactoring the Everything server to demonstrate how servers can avail themselves of the SDK's recent addition of Automatic handling of logging level, I discovered a wrinkle that needs ironing out.

STDIO server connections (which do not have a sessionId) would no longer throw a "Method not found" error if they advertised logging but did not set a listener for SetLevelRequestSchema messages, which is good. However, they would not respect the level that was set in subsequent calls to sendLoggingMessage. This is because the log levels are tracked by sessionId, to allow for multiple clients connecting to a server and each setting their own level.

This PR fixes that and tests the entire process, both with and without a sessionId.

How Has This Been Tested?

New unit tests for both cases.

Breaking Changes

Nope.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context