Windows 10/11 - can't Connect to MCP Inspector app

[onemen]

I can not connect to the MCP inspector app

Proxy Session Token in the config is not the same as the one in the terminal., but event when i copy it to the config it did not help

clicking on 'OAuth settings also fails'

[onemen]

There is an issue with the sever prefix advanced-mcp-features

The workshop app is actually running in http://advanced-mcp-features.localhost:5639

🐨  Let's get learning!
Local:            http://localhost:5639
On Your Network:  http://10.100.102.21:5639


🌐 Opening browser to http://advanced-mcp-features.localhost:5639 ...

when i run the playground app, although the console print Proxy server running: http://localhost:4000

[playground:4000] Starting MCP inspector...
[playground:4000]
[playground:4000] ⚙️ Proxy server listening on localhost:10000
[playground:4000]
[playground:4000] 🔑 Session token: fc5c46b796e558efa7806390ba781abd2bfea0dfe65d1bb16642517ca5e9ebe8
[playground:4000]    Use this token to authenticate requests or set DANGEROUSLY_OMIT_AUTH=true to disable auth
[playground:4000]
[playground:4000] 🐨 Proxy server running: http://localhost:4000
[playground:4000]
[playground:4000] - Client port: 9000
[playground:4000] - Server port: 10000
[playground:4000]

The app is opened in http://advanced-mcp-features.localhost:4000
with the path: http://advanced-mcp-features.localhost:4000/?transport=stdio&serverCommand=npm&serverArgs=--silent+--prefix+%22E%3A%5Cprojects%5Ckcd-apps%5Cadvanced-mcp-features%5Cplayground%22+run+dev%3Amcp&MCP_PROXY_AUTH_TOKEN=c139364b86c1c02b4ae5916128c94013d9dad7c5ff6854e1381fa2dbd11dcfa5&MCP_PROXY_FULL_ADDRESS=http%3A%2F%2Flocalhost%3A10000&MCP_REQUEST_MAX_TOTAL_TIMEOUT=900000&MCP_SERVER_REQUEST_TIMEOUT=300000#resources

if I open it manually from http://localhost:4000 by clicking the link in the console and then modify the token manually by copying the token that appears in the console it worked

[kentcdodds]

This is the logic for the auto-fill stuff we do for the inspector: https://github.com/epicweb-dev/advanced-mcp-features/blob/main/epicshop/mcp-dev/dev.js

We do this because I don't want people to have to fill in those details during the workshop. It's just annoying busy work.

This workshop doesn't deal with oauth so that stuff won't work. But the token should definitely work. What do you suppose could be the issue?

[onemen]

I see the same on Linux, using Oracle VirtualBox

The app is opened in http://advanced-mcp-features.localhost:4000
with the path: http://advanced-mcp-features.localhost:4000/?transport=stdio&serverCommand=npm&serverArgs=--silent+--prefix+%22E%3A%5Cprojects%5Ckcd-apps%5Cadvanced-mcp-features%5Cplayground%22+run+dev%3Amcp&MCP_PROXY_AUTH_TOKEN=c139364b86c1c02b4ae5916128c94013d9dad7c5ff6854e1381fa2dbd11dcfa5&MCP_PROXY_FULL_ADDRESS=http%3A%2F%2Flocalhost%3A10000&MCP_REQUEST_MAX_TOTAL_TIMEOUT=900000&MCP_SERVER_REQUEST_TIMEOUT=300000#resources

When i manually open the app in new tab using http://localhost:4000.....
it work when I manually copy the Session token from the console