zen-atlas-mcp-proxy

HTTP-to-stdio proxy for connecting Claude Desktop and other MCP clients to Zen Atlas MCP servers deployed on Railway or other cloud platforms.

Installation

npm install -g zen-atlas-mcp-proxy

Quick Start

1. Get your server URL from Railway deployment
2. Generate an auth token (see server documentation)
3. Configure your MCP client:

Claude Desktop Configuration

Add to your Claude Desktop config:

{
  "mcpServers": {
    "zen-atlas": {
      "command": "zen-atlas-mcp-proxy",
      "args": ["https://your-server.railway.app"],
      "env": {
        "ZEN_MCP_TOKEN": "your-secret-token"
      }
    }
  }
}

Command Line Usage

# With token in environment
export ZEN_MCP_TOKEN=your-secret-token
zen-atlas-mcp-proxy https://your-server.railway.app

# Or specify server via environment
export ZEN_MCP_SERVER_URL=https://your-server.railway.app
export ZEN_MCP_TOKEN=your-secret-token
zen-atlas-mcp-proxy

Features

• 🔒 Secure: Bearer token authentication
• 🌐 Universal: Works with any MCP client
• ⚡ Fast: Minimal overhead proxying
• 🔄 Reliable: Automatic error handling
• 📦 Lightweight: Minimal dependencies

How It Works

The proxy acts as a bridge between MCP clients (which expect stdio communication) and HTTP-based MCP servers:

[MCP Client] <--stdio--> [zen-atlas-mcp-proxy] <--HTTP--> [Railway Server]

Security

Always use authentication in production:

1. Generate a secure token on your server
2. Add the token to Railway environment variables
3. Configure the proxy with the same token

Troubleshooting

Connection Failed

• Check your server URL is correct
• Verify the server is running (visit /health endpoint)
• Ensure your token matches the server configuration

Authentication Errors

• Verify ZEN_MCP_TOKEN is set correctly
• Check the token doesn't have extra spaces or quotes
• Regenerate the token if needed

License

MIT