Remote-MCP Issue: Claude tool not available without Active VS Code connection

[Odysseus-deep]

Description
When using Remote-MCP to integrate custom tools with Claude, the tools are only available while VS Code is actively connected to the server. Once VS Code is disconnected, Claude can no longer access the tools, even though both the Node.js Remote-MCP server (port 9512) and Python backend server (port 8001) continue running correctly.

Environment
Ubuntu server (VPS)
Node.js v20.19.0 (via NVM)
Systemd service for Remote-MCP server
Python FastAPI backend for LlamaCloud integration
VS Code with Remote-SSH extension

Steps to Reproduce
Connect to server via VS Code Remote-SSH
Verify that Claude can access the custom tool
Disconnect from VS Code
Try to use the custom tool in Claude - it's no longer available

Current Workaround
The only working solution is to keep VS Code connected to the server at all times, which is not practical for production environments.
Investigation Results

The Node.js Remote-MCP server runs correctly (verified with systemctl status)
The Python FastAPI server runs correctly (verified with curl requests)
Both servers remain active even after VS Code disconnects
The issue appears to be related to how VS Code registers the tools with Claude

Request
Is there a way to maintain tool registration with Claude without requiring an active VS Code connection?
Ideally, we would like to deploy these tools to a production server where they remain available to Claude without depending on an active VS Code session.