Skip to main content

Server Deployment Wizard

The Deployment Wizard guides you through deploying MCP servers from the registry to your infrastructure. This streamlined process ensures proper configuration and security settings.

Starting the Deployment​

Prerequisites​

Before deploying:

  • Server must be in "Published" status
  • Target environment must be prepared
  • Necessary credentials must be available
  • Helmet CLI must be installed on target machine

Accessing the Wizard​

  1. Navigate to the Servers section
  2. Click "Deploy Server" button
  3. Select the server you want to deploy
  4. Choose deployment method

Deployment Methods​

Stdio (Standard Input/Output)​

The most common deployment method for local and development environments.

Use Cases:

  • Local development servers
  • Command-line tools
  • Simple integrations

How it Works:

  • Direct process communication
  • No network overhead
  • Immediate response
  • Simple debugging

SSE (Server-Sent Events) - Coming Soon​

For real-time streaming applications.

HTTP Streaming - Coming Soon​

For real-time streaming applications.

Stdio Deployment Process​

Step 1: Select Server​

Choose from your published servers:

  • Search by name
  • Filter by type
  • View server details
  • Check compatibility

Step 2: Choose Transport Type​

Select Stdio for standard communication:

  • Best for command-line tools
  • Minimal latency
  • Direct process control
  • Easy troubleshooting

Step 3: Configure Deployment​

Source Type​

Container Deployment

  • Uses Docker for isolation
  • Consistent environment
  • Easy scaling
  • Resource limits

Configuration includes:

  • Container image URL
  • Resource allocation
  • Environment variables
  • Volume mounts

Step 4: Environment Variables​

Configure required variables:

  • API keys and tokens
  • Database connections
  • Service endpoints
  • Feature flags

Security Note: Sensitive values are encrypted and transmitted securely.

Step 5: Generate Configuration​

The wizard creates a deployment configuration containing:

  • MCP server settings
  • Helmet proxy configuration
  • Security tokens (7-hour expiration)
  • Environment setup

Deployment Configuration​

Understanding the Output​

The generated configuration includes:

{
  "mcpServers": {
    "your-server": {
      "command": "helmet",
      "args": [
        "docker",
        "run",
        "-i",
        "--rm",
        "-e",
        "REDIS_HOST=value",
        "mcp/redis"
      ],
      "env": {
        "CONTAINER_IMAGE": "mcp/redis",
        "HELMET_SESSION_TOKEN": "eyJhb..."
      }
    }
  }
}

Security Tokens​

  • Session Token: Temporary authentication (7 hours)
  • Automatic Refresh: Tokens refresh during active use
  • Secure Storage: Never commit tokens to version control
  • Revocation: Can be revoked from dashboard

Using the Configuration​

  1. Copy Configuration: Click the copy button
  2. Install Helmet CLI: Follow installation instructions
  3. Configure MCP Client:
    • Open Claude Desktop, Cursor, or VS Code
    • Navigate to MCP Servers settings
    • Paste the configuration
  4. Save and Connect: The server is now available

Post-Deployment​

Verification​

After deployment:

  • Check server status in dashboard
  • Verify logs show successful startup
  • Test basic functionality
  • Monitor initial performance

Monitoring​

The deployed server will show:

  • Real-time status updates
  • Request/response logs
  • Performance metrics
  • Error tracking

Management​

From the Servers dashboard:

  • View detailed logs
  • Monitor resource usage
  • Track client connections
  • Manage lifecycle

Deployment Best Practices​

Troubleshooting Deployment​

Common Issues​

Token Expiration

  • Generate new configuration
  • Update client settings
  • Restart connection

Connection Failures

  • Verify network connectivity
  • Check firewall rules
  • Confirm token validity
  • Review server logs

Debug Mode​

Enable detailed logging:

  • Set HELMET_LOG_LEVEL=DEBUG
  • Check verbose output
  • Capture error traces
  • Share with support

Next Steps​

After successful deployment: