How to configure Claude Desktop/Cursor for a remote MCP Memory Service?

[cheonmux]

Hi everyone,

I've successfully set up the doobidoo/mcp-memory-service on my VPS. I can access the web dashboard perfectly at http://my-vps-ip:8000, and everything looks healthy.

Now I'm stuck on the client-side configuration. The documentation I've found mainly shows how to launch the service locally using command and args in the claude_desktop_config.json.

My question is: How do I configure Claude Desktop and Cursor to connect to my remote server endpoint (https://:8000/mcp) instead of launching a local process?

I also have an API key set on the server, so I'll need to know how to include that in the configuration as well.

What should the JSON configuration look like for a remote connection?

Thanks for any help!

[doobidoo]

✅ Solution Added to Wiki!

Hey! Great question about remote MCP Memory Service configuration. I've just added comprehensive documentation to the wiki that covers exactly what you need.

🎯 Complete Solution Now Available

📚 Location: 03 Integration Guide - Remote Server Configuration

🔧 Quick Answer for Your Setup

Here's the exact JSON configuration you need for Claude Desktop:

{
  "mcpServers": {
    "memory": {
      "command": "node",
      "args": ["/path/to/mcp-memory-service/examples/http-mcp-bridge.js"],
      "env": {
        "MCP_MEMORY_HTTP_ENDPOINT": "https://your-vps-ip:8000/api",
        "MCP_MEMORY_API_KEY": "your-secure-api-key"
      }
    }
  }
}

🚀 What You Need to Do

1. Download the HTTP Bridge: Get examples/http-mcp-bridge.js from the repository
2. Update Configuration: Add the JSON above to your Claude Desktop config file
3. Replace Values:
   • Change /path/to/mcp-memory-service/examples/http-mcp-bridge.js to the actual file path
   • Replace https://your-vps-ip:8000/api with your VPS endpoint
   • Add your actual API key
4. Restart Claude Desktop

📖 Complete Documentation

The new wiki section includes:

• ✅ Step-by-step setup instructions
• ✅ Multiple configuration options (manual endpoint vs auto-discovery)
• ✅ Environment variables reference
• ✅ Comprehensive troubleshooting guide for common remote connection issues
• ✅ Links to complete example files

🛠️ The HTTP-to-MCP Bridge

The solution uses the existing http-mcp-bridge.js that's already in the repository. It translates HTTP API calls to MCP protocol messages, allowing remote connections with full support for:

• API key authentication
• HTTPS with self-signed certificates
• Retry logic and error handling
• Comprehensive logging for troubleshooting

This should get your remote setup working perfectly! Let me know if you run into any issues following the guide.