Manually Setting Authentication Header still requires oauth flow

[rob893]

Describe the bug
I manually set the authentication header:

however the inspector still tries to go through the oauth flow which won't work because the provider endpoints it tries to use do no support cors.

To Reproduce
Steps to reproduce the behavior:

1. Manually set the authentication header
2. Connect to MCP
3. notice it still tries to go through oauth flow

Expected behavior
If the authentication header is manually set, inspector should just use it rather than trying to go through the oauth flow.

The MCP server in question uses C# sdk with entra auth

[cliffhall]

Hi @rob893!

1. Please try with the latest version of the Inspector. I can tell you're using an older version because the options in the Authentication tab are different from the latest version which look like this:

2. Here, I'm connecting to the server-everything reference server which does not require auth, but I'm passing a Bearer token anyway. You can see that it connects without attempting OAuth and the Authorization header is in the request.

Screen.Recording.2025-09-05.at.4.18.45.PM.mov

Closing for now, feel free to reopen if you have trouble with the latest version of the Inspector.