Mohammed Omar Miraj

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.

Judging from your error message, you are trying to translate a `usize` which the typescript typeshare does not support currently as seen in `core/src/language/typescript.rs`

Hello folks, sorry for this we have identified the issue and the fix will be up shortly.. will let you folks know when to retry your pipelines

A fix has been pushed, please let me know if that has fixed it for you!

Hey Folks, Just wanted to know what is currently blocking this MR and if needed how I can help. This would be awesome to get merged in considering the latest...

Hmm do you mean https://github.com/modelcontextprotocol/typescript-sdk/pull/503 (this is server side) and this is client side https://github.com/modelcontextprotocol/typescript-sdk/pull/416 unless im missing something.

> @pcarleton mentioned [this one](https://github.com/modelcontextprotocol/typescript-sdk/issues/672) when I asked in Discord. But I'm not certain that keeps 401 from reaching the client, it's just related to scopes. So I'll look into...

I see in the request that it is exposed and when I try to start the server.. it immediately runs the OAuth flow and tries to fetch the `.well-known/oauth-protected-resource` etc.....

Ahh sorry for the confusing report, I do see the 401 and then it continues with the OAuth Flow. See attached picture as you can see at the top with...

This is the image with no `WWW-Authenticate`  and this is the image with `WWW-Authenticate`