[mcp] server handler for streamable HTTP transport

[greedy52]

Part of:

• MCP access streamable HTTP support #56588

Run a MCP server in streamable HTTP transport, for example:

npx @modelcontextprotocol/server-everything streamableHttp

App definition:

  - name: "everything-http"
    uri: "mcp+http://localhost:3001/mcp"
    labels:
      env: dev

Start local proxy:

tsh proxy app -p 8888 everything-http

Connect with inspector (npx @modelcontextprotocol/inspector):

Connect with Claude Desktop

{
  "mcpServers": {
    "teleport-mcp-everything-http": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:8888/mcp",
        "--transport",
        "http-only"
      ]
    }
  }
}

[Tener]

This works, but I wonder if we can pass ctx somewhere to have this automated?

[greedy52]

this is a tough one. i updated the code to pass the ctx as base context. but even then, it's up to many parts of the handler flow to honor the ctx or not. So i kept the go routine just to be sure. ebdad41

[gabrielcorado]

Given that we're closing the connection after the function returns (due to defer cancel()), wouldn't it make sense to have it all on a single defer call?

defer func() {
	cancel() // relevant to handler.
	waitConn.Close() // Ensure connection is closed
}()

[greedy52]

Given that we're closing the connection after the function returns (due to defer cancel()), wouldn't it make sense to have it all on a single defer call?

defer func() {
	cancel() // relevant to handler.
	waitConn.Close() // Ensure connection is closed
}()

the situation we are trying to resolve is when the input ctx is canceled outside this handler func. there is a long chain of functions from http server to mcputils through all the connection handling. when things implemented correctly, everything shuts down when parent ctx is canceled. again, if implemented correctly. so I just don't want to risk that so i explicitly close the connection when input context is canceled.

[gabrielcorado]

LGTM just some minor comments.