# ============================================ # ALZ Discovery Sample - Environment Variables # ============================================ # Generated by Agent Builder Platform # # SETUP INSTRUCTIONS: # 1. Copy this file to .env: cp .env.example .env # 2. Generate a secure API key: openssl rand -hex 32 # 3. Update MCP_REGISTRATION_API_KEY with the generated key # 4. Build the image from the Dockerfile and run it where the MCP Gateway # can reach it (see README.md) # # MCP GATEWAY INTEGRATION: # When registering with the MCP Gateway, use the URL the Gateway reaches this # server at; for a container on the Gateway's network, its container name: # http://alz-discovery-sample:8110 # ============================================ # Server Identity MCP_SERVER_NAME=ALZ Discovery Sample MCP_SERVER_ID=alz-discovery-sample MCP_SERVER_VERSION=0.1.0 # Server Configuration MCP_SERVER_PORT=8110 # Logging: level (DEBUG, INFO, WARNING, ERROR) and format # (json = one object per line, for log stores; console = for reading by eye) LOG_LEVEL=INFO LOG_FORMAT=json # ============================================ # AUTHENTICATION (REQUIRED for production!) # ============================================ # This key authenticates MCP Gateway requests to this server. # The Gateway stores this key and includes it in all tool/call requests. # # Generate a secure key: # openssl rand -hex 32 # # IMPORTANT: Keep this key secret! It's stored in: # - This .env file (gitignored) # - MCP Gateway database (encrypted) MCP_REGISTRATION_API_KEY= # Set to "false" ONLY for local development/testing # WARNING: Disabling auth in production is a security risk! REQUIRE_AUTH=true # ============================================ # Add your own settings below # ============================================ # Do not put credentials for an upstream system here: declare them as connection fields # in the MCP Server Builder so each tenant supplies its own. # EXAMPLE_SETTING=value