Response in HTTP format

[dev-gbassanini]

Describe the bug
When using the MCP server in HTTP mode, it responds back in SSE format instead of HTTP/JSON

To Reproduce
Steps to reproduce the behavior:
Connect to the MCP via a client: MCP Inspector, Cline, simple curl, etc
List tools
Get problems

Expected behavior
Get an HTTP/JSON format response. SSE is returned instead

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[christian-kreuzberger-dtx]

Could this be related to #134 ?

I'm trying the same, and it works fine with @modelcontextprotocol/inspector (with the fix of #145 )

[dev-gbassanini]

This is what I meant: (Using the MCP with the http flag)
----HTTP-JSON Format
Expected: Pure JSON response back from MCP
eg:
{"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2024-11-05","capabilities":{"tools":{}},"serverInfo":{"name":"dynatrace-mcp-server","version":"0.5.0"}}}

But what I get:

Content-Type: application/json
< Content-Type: text/event-stream
< mcp-session-id: 2fa9da67-1ccd-45da-9965-fbc6c9bd52e0
event: message
data: {"result":{"protocolVersion":"2024-11-05","capabilities":{"tools":{"listChanged":true}},"serverInfo":{"name":"Dynatrace MCP Server","version":"0.5.0"}},"jsonrpc":"2.0","id":1}

Key Differences Summary:
HTTP-JSON: Content-Type: application/json, single response, stateless
SSE: Content-Type: text/event-stream, event/data format, session-based

It seems StreamableHTTPServerTransport is hardcoded to return SSE format only

[dev-gbassanini]

Something like this: transport.setResponseFormat('json'); would be very nice to have. But it currently doesn't exist

[christian-kreuzberger-dtx]

We are using standard transport mechanism of ModelContextProtocol, primarily Streamable HTTP Transport.

Could you please try if this is still a problem with latest release 0.7.0?

[christian-kreuzberger-dtx]

Closing this as this issue is stale.