Configuration

Advanced configuration options for Tetrix AI MCP Server integration. Customize your setup for optimal performance, security, and functionality.

Basic Configuration

The standard Tetrix AI MCP server configuration works out of the box:


{
  "mcpServers": {
    "tetrix": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "http://tetrix-level-1-dev-alb-463220232.us-east-1.elb.amazonaws.com/mcp",
        "--transport",
        "http-only",
        "--allow-http"
      ]
    }
  }
}

Advanced Configuration Options

Environment Variables

Configure Tetrix AI behavior using environment variables:


{
  "mcpServers": {
    "tetrix": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "http://tetrix-level-1-dev-alb-463220232.us-east-1.elb.amazonaws.com/mcp",
        "--transport",
        "http-only",
        "--allow-http"
      ],
      "env": {
        "TETRIX_LOG_LEVEL": "info",
        "TETRIX_TIMEOUT": "30000",
        "TETRIX_CACHE_TTL": "300",
        "NODE_ENV": "production"
      }
    }
  }
}

Available Environment Variables:

Variable	Default	Description
`TETRIX_LOG_LEVEL`	`info`	Logging level: `debug`, `info`, `warn`, `error`
`TETRIX_TIMEOUT`	`30000`	Request timeout in milliseconds
`TETRIX_CACHE_TTL`	`300`	Cache time-to-live in seconds
`TETRIX_MAX_RETRIES`	`3`	Maximum retry attempts for failed requests
`NODE_ENV`	`development`	Node.js environment

Working Directory

Set a specific working directory for the MCP server:


{
  "mcpServers": {
    "tetrix": {
      "command": "npx",
      "args": [...],
      "cwd": "/path/to/your/project"
    }
  }
}

Timeout Configuration

Adjust timeout settings for different scenarios:


{
  "mcpServers": {
    "tetrix": {
      "command": "npx",
      "args": [...],
      "timeout": 60000,
      "env": {
        "TETRIX_CONNECT_TIMEOUT": "10000",
        "TETRIX_REQUEST_TIMEOUT": "30000",
        "TETRIX_IDLE_TIMEOUT": "300000"
      }
    }
  }
}

Platform-Specific Configuration

Claude Desktop

macOS Configuration Location:


~/Library/Application Support/Claude/claude_desktop_config.json

Advanced Claude Desktop Configuration:


{
  "mcpServers": {
    "tetrix": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "http://tetrix-level-1-dev-alb-463220232.us-east-1.elb.amazonaws.com/mcp",
        "--transport",
        "http-only",
        "--allow-http"
      ],
      "env": {
        "CLAUDE_INTEGRATION": "true",
        "TETRIX_UI_MODE": "conversational"
      }
    }
  },
  "globalSettings": {
    "mcpTimeout": 45000,
    "enableDebugLogging": false
  }
}

Cursor IDE

Cursor-Specific Settings:


{
  "mcp": {
    "servers": {
      "tetrix": {
        "command": "npx",
        "args": [
          "-y",
          "mcp-remote@latest",
          "http://tetrix-level-1-dev-alb-463220232.us-east-1.elb.amazonaws.com/mcp",
          "--transport",
          "http-only",
          "--allow-http"
        ],
        "env": {
          "CURSOR_INTEGRATION": "true",
          "TETRIX_UI_MODE": "inline",
          "TETRIX_CODE_CONTEXT": "true"
        }
      }
    },
    "settings": {
      "autoConnect": true,
      "reconnectOnFailure": true,
      "maxReconnectAttempts": 5
    }
  }
}

Performance Optimization

Connection Pooling

For high-volume usage, configure connection pooling:


{
  "mcpServers": {
    "tetrix": {
      "command": "npx",
      "args": [...],
      "env": {
        "TETRIX_POOL_SIZE": "5",
        "TETRIX_POOL_TIMEOUT": "30000",
        "TETRIX_KEEP_ALIVE": "true"
      }
    }
  }
}

Caching Configuration

Optimize response times with intelligent caching:


{
  "mcpServers": {
    "tetrix": {
      "command": "npx",
      "args": [...],
      "env": {
        "TETRIX_CACHE_ENABLED": "true",
        "TETRIX_CACHE_SIZE": "100MB",
        "TETRIX_CACHE_TTL": "600",
        "TETRIX_CACHE_STRATEGY": "lru"
      }
    }
  }
}

Resource Limits

Set resource limits to prevent excessive usage:


{
  "mcpServers": {
    "tetrix": {
      "command": "npx",
      "args": [...],
      "env": {
        "TETRIX_MAX_MEMORY": "512MB",
        "TETRIX_MAX_REQUESTS_PER_MINUTE": "60",
        "TETRIX_MAX_CONCURRENT_REQUESTS": "10"
      }
    }
  }
}

Security Configuration

Authentication

While Tetrix AI MCP Server currently uses a public endpoint, you can configure additional security:


{
  "mcpServers": {
    "tetrix": {
      "command": "npx",
      "args": [...],
      "env": {
        "TETRIX_API_KEY": "your-api-key",
        "TETRIX_USER_AGENT": "YourApp/1.0",
        "TETRIX_ORIGIN": "your-domain.com"
      }
    }
  }
}

Network Security

Configure network-level security:


{
  "mcpServers": {
    "tetrix": {
      "command": "npx",
      "args": [...],
      "env": {
        "TETRIX_ALLOWED_HOSTS": "tetrix-level-1-dev-alb-463220232.us-east-1.elb.amazonaws.com",
        "TETRIX_SSL_VERIFY": "true",
        "TETRIX_PROXY": "http://your-proxy:8080"
      }
    }
  }
}

Debugging Configuration

Debug Logging

Enable detailed logging for troubleshooting:


{
  "mcpServers": {
    "tetrix": {
      "command": "npx",
      "args": [...],
      "env": {
        "DEBUG": "tetrix:*,mcp:*",
        "TETRIX_LOG_LEVEL": "debug",
        "TETRIX_LOG_FILE": "/tmp/tetrix-mcp.log",
        "TETRIX_TRACE_REQUESTS": "true"
      }
    }
  }
}

Development Mode

Configuration for development and testing:


{
  "mcpServers": {
    "tetrix": {
      "command": "npx",
      "args": [...],
      "env": {
        "NODE_ENV": "development",
        "TETRIX_DEV_MODE": "true",
        "TETRIX_MOCK_RESPONSES": "false",
        "TETRIX_VERBOSE": "true"
      }
    }
  }
}

Multiple Server Configuration

Running Multiple Tetrix Instances

Configure multiple Tetrix AI servers for different purposes:


{
  "mcpServers": {
    "tetrix-dev": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "http://tetrix-level-1-dev-alb-463220232.us-east-1.elb.amazonaws.com/mcp",
        "--transport",
        "http-only",
        "--allow-http"
      ],
      "env": {
        "TETRIX_ENVIRONMENT": "development"
      }
    },
    "tetrix-prod": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "http://tetrix-level-1-prod-alb-123456789.us-east-1.elb.amazonaws.com/mcp",
        "--transport",
        "http-only",
        "--allow-http"
      ],
      "env": {
        "TETRIX_ENVIRONMENT": "production"
      }
    }
  }
}

Mixed MCP Servers

Combine Tetrix AI with other MCP servers:


{
  "mcpServers": {
    "tetrix": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "http://tetrix-level-1-dev-alb-463220232.us-east-1.elb.amazonaws.com/mcp",
        "--transport",
        "http-only",
        "--allow-http"
      ]
    },
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/project"]
    },
    "git": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-git", "/path/to/repo"]
    }
  }
}

Configuration Validation

Syntax Checking

Validate your configuration file syntax:


# For JSON files
cat claude_desktop_config.json | jq .
 
# For YAML files (if supported)
yamllint config.yaml

Connection Testing

Test your configuration:


# Test the MCP connection directly
npx -y mcp-remote@latest http://tetrix-level-1-dev-alb-463220232.us-east-1.elb.amazonaws.com/mcp --transport http-only --allow-http --test-connection
 
# Check Node.js and npx availability
node --version
npx --version

Configuration Best Practices

1. Start Simple

Begin with the basic configuration and add complexity as needed.

2. Environment-Specific Configs

Use different configurations for development, staging, and production.

3. Security First

Never commit API keys or sensitive data to version control
Use environment variables for sensitive configuration
Regularly review and rotate credentials

4. Performance Monitoring

Monitor connection times and response rates
Adjust timeouts based on your usage patterns
Use caching to improve response times

5. Documentation

Document your configuration choices
Keep configuration files in version control (without secrets)
Share best practices with your team

Troubleshooting Configuration

Common Issues

Configuration not recognized:

Check JSON syntax and formatting
Verify file location and permissions
Restart your MCP client after changes

Connection failures:

Verify network connectivity
Check firewall and proxy settings
Validate environment variables

Performance issues:

Adjust timeout settings
Enable caching
Monitor resource usage

Getting Help

📖 Check our Troubleshooting Guide
💬 Ask in GitHub Discussions
🔍 Review API Reference for technical details

Configuration complete! Your Tetrix AI MCP Server is now optimized for your specific needs and environment.