Skip to main content
Glama

MCP Linux Deployment

by dnchandra
.env.example1.12 kB
[hunter@web2 scripts]$ cat /home/hunter/MCPServer/.env # MCP Server Configuration - Linux Standalone Deployment # Copy this file to .env and update with your values # Backend API Configuration # URL of the Windows Server Dashboard backend API WIN_DASH_API_BASE="http://192.168.1.70:8000" # Optional: Backend API token if your API requires authentication # BACKEND_API_TOKEN=your-backend-token-here # MCP Server Configuration # Host to bind the MCP server (0.0.0.0 for all interfaces, 127.0.0.1 for localhost only) MCP_HOST=0.0.0.0 # Port for the MCP server MCP_PORT=3000 # Security Configuration # MCP API token for client authentication (leave empty to disable authentication) # Generate a secure token: openssl rand -hex 32 MCP_API_TOKEN="test-token-please-change" # Default Windows Credentials # These will be used if not provided in individual requests # IMPORTANT: Use proper credentials management in production (e.g., HashiCorp Vault, Azure Key Vault) WIN_DEFAULT_USER="Administrator" WIN_DEFAULT_PASS="Admin@123" # Logging Configuration # Log level: DEBUG, INFO, WARNING, ERROR, CRITICAL LOG_LEVEL=INFO

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dnchandra/mcp_linux'

If you have feedback or need assistance with the MCP directory API, please join our Discord server