Development and inspection of MCP Server on a remote VM?

[saminbatra29]

Pre-submission Checklist

• I have checked that this question would not be more appropriate as an issue in a specific repository
• I have searched existing discussions and documentation for answers

Question Category

• Protocol Specification
• SDK Usage
• Server Implementation
• General Implementation
• Documentation
• Other

Your Question

Hello,

I am implementing an MCP server on a remote VM where it will run in the future and be accessed by other MCP client(s). I read that we can use MCP inspector to debug and test changes we make to any tools or prompts.
However, when I run the server using the command "mcp dev <file_name.py>" or even "npx @modelcontextprotocol/inspector uv run <file_name.py>", I can access the inspector portal that is running in the VM from my local machine, however when I try to connect to the MCP server from the inspector, it says "Error Connecting to MCP Inspector Proxy - Check Console logs"

I have tried STDIO and SSE type transportation protocols but no luck. I also tried implementing my own MCP client to connect to this server and that was able to connect (they are running on the same VMs)
Anyone faced a similar issue?

[naji247]

You would need to make sure the ports are exposed on the remote host and incoming and outgoing network requests are allowed. Unfortunately this might be more of an infrastructure issue than an issue with the protocol. Did you end up resolving the issue?