ln-12

We are facing the same issue. The [official documentation](https://modelcontextprotocol.io/specification/2025-06-18/basic/transports#session-management) states that: ``` When a client receives HTTP 404 in response to a request containing an Mcp-Session-Id, it MUST start a...

Alright, then a possible solution for now seems to be to only run the server on one host. Thanks for the clarification!

@jba From [this thread](https://github.com/modelcontextprotocol/typescript-sdk/issues/330) on the typescript sdk I found [this documentation](https://github.com/modelcontextprotocol/typescript-sdk/tree/main/src/examples#multi-node-deployment) that described multi node deployment configurations. For my current use case, it would be enough to turn off...

I played around with the source code and got a seemingly working solution for which I created a draft: https://github.com/modelcontextprotocol/go-sdk/pull/159 For the quick testing I did, it seems to work...

Yes, we currently only have some kind of search tool which means all information needed is provided through the arguments of the tool. For now, we deployed my fork of...

I would still prefer the option to turn session validation off. In our scenario, we don't need it at all and also don't want to maintain a DB for it....

I just checked again after updating to version 6.1.1 and for me this still gives the warning mentioned above when I rebuild my project. It happens in the `compileDebugKotlin` task.

I still get an error after the release of 0.17.4 unfortunately: ``` $ npx modelcontextprotocol/inspector Need to install the following packages: github:modelcontextprotocol/inspector Ok to proceed? (y) y npm error code...