Issue

mcp-handler@1.1.0 declares @modelcontextprotocol/sdk as a peer dependency at exactly 1.26.0. This makes npm reject projects using newer MCP SDK 1.x versions, such as 1.31.0, unless they disable peer dependency checks.

The 1.1.0 changelog describes 1.26.0 as a minimum, and the security advisory says >=1.26.0. The published exact peer pin appears narrower than that intent.

Reproduction

In a fresh npm project:

npm install mcp-handler@1.1.0 @modelcontextprotocol/sdk@1.31.0

npm exits with ERESOLVE because the handler requires SDK 1.26.0 exactly.

Request

Could you confirm whether mcp-handler 1.x supports newer MCP SDK 1.x releases and, if so, publish a 1.x patch release with a compatible peer range (for example, >=1.26.0 <2.0.0)?

The request is to confirm and test it before widening the peer range.

Activity

No activity yet.