Cliff Hall

Response headers. Can you show them? You posted the request headers. ~~Your screenshot doesn't support this statement; it doesn't talk about the URL.~~ Also, my bad on that part I...

Ok, thanks @MOmarMiraj for your help. I'm going to have to figure out a good way to test this locally.

> I believe the issue lies in the SDK not accepting a custom fetch function. I believe you are correctly overriding it but inside the `StreamableHTTPClient` class in the MCP...

Waiting on https://github.com/modelcontextprotocol/typescript-sdk/pull/721

@MOmarMiraj could you try this again? You'll need to run `npm install` again, and should be using sdk version 1.15.0, which has the [support for custom fetch](https://github.com/modelcontextprotocol/typescript-sdk/pull/721) that this PR...

> When running inspector you should be able to specify the transport type to use, or it should be inferred from the server provided (eg: if it's `http(s)` prefixed, using...

Could we not rectify the situation in the client app, so that if you have supplied an http(s) url it switches the type to SSE?

This is related to https://github.com/modelcontextprotocol/inspector/issues/495#issuecomment-2952820238 If you set the environment var `SERVER_PORT` to something other than 6277 before launching, the proxy server will launch on the specified port, but the...

We really need something in the "how has this been tested" section of these PRs, particularly if it hooks into CI.

> > We really need something in the "how has this been tested" section of these PRs, particularly if it hooks into CI. > > I'll update that section, but...