How to run this tool and use it when my MCP server is a remote server?

[Rickcau]

Describe the bug
I need to be able to use this tool to inspect a remote MCP server.

To Reproduce
Steps to reproduce the behavior:
1.

Expected behavior
A clear and concise description of what you expected to happen.

Logs
If applicable, add logs to help explain your problem.

Additional context
Add any other context about the problem here.

[cliffhall]

Have you tried putting the url here:

[Rickcau]

I have. When I open the console log in browsers for some reason it's trying to connecting it looks like the NMCP proxy is experiencing a CORS issue. I will have to look into this tomorrow.

[Larmyliu]

@Rickcau
In version 0.7.0, you can directly open the webpage using the IP for debugging.

[Yi-Liang-Leon]

I'm facing the same problem, which was not happening in 0.6.0.

[cliffhall]

@Yi-Liang-Leon @Rickcau for troubleshooting, can either of you provide the url of a remote server you're getting the problem with?

[Yi-Liang-Leon]

It is a docker container on a internal machine, with entrypoint npx -y supergateway --port 8080 --cors --stdio "npx -y @modelcontextprotocol/server-gitlab". The port are correctly exposed and the network is working well (since I can succesfully connect to it in 0.6.0).

[olaservo]

Hi, checking back on this one - I'm curious to confirm whether this issue can be resolved using @Larmyliu 's suggestion above?

[olaservo]

Closing this one but please feel free to re-open if you're still having issues.