Cliff Hall

> @cliffhall I'm not sure if your approval of this PR was in pursuit of actually merging it; in case it was: I think there is a lot to unravel...

> @dsp-ant -> #993 > > @cliffhall maybe you'd be willing to sponsor? @patwhite I'd love to. This is a feature I'm excited about and I want to see it...

I agree that this makes sense. However, with the very recent addition of `streamable-http` transport and continued support for `sse` I don't think a single `sseUrl` is the full solution....

Hi @xiaoyijun! Thanks for this. I haven't done a local test of it yet, but I like what I see in the PR description and it does make sense for...

> Tested by connecting to an MCP server requiring OAuth authentication without dynamic client registration capabilities. @xiaoyijun can you drop a link to the server you tested with? I'd really...

> I will update this PR once [modelcontextprotocol/typescript-sdk#491](https://github.com/modelcontextprotocol/typescript-sdk/pull/491) is merged, and will also include the `scope` settings in the "OAuth Configuration" section so that you can test smoothly. Nice one,...

> Previously, we could initiate the auth flow directly during the connection process. However, now I notice that the Inspector redirects to `http://localhost:6277/authorize`, while we actually need to redirect to...

@xiaoyijun Is there a way you could test this against an example server in the TypeScript SDK? I'm wary of installing random code for testing, and would much rather test...

> Quick question here, does any MCP client even support this type of flow? I see all MCP clients force DCR when the spec doesn't enforce it. @MOmarMiraj * VSCode...

@xiaoyijun Sorry to have let this one slip through the cracks. Could you resolve conflicts, so I can test?