Generic EnergyNetWatch MCP Setup

Use this setup model for MCP-compatible clients that can run a local server command with environment variables.

Codex setup Security guidance

MCP-compatible client

Use a client that can run a local MCP server command with environment variables.

Approved API key

Create the key in EnergyNetWatch API Access after the account has active API or MCP entitlement.

Secure environment

Store the key in a local environment variable or managed secret input.

Network access

The local server must reach https://api.energynetwatch.com. It does not connect directly to RDS.

Smoke test

Start with health, data availability, or a single operator search before broad workflows.

Generic config shape

{
  "mcpServers": {
    "energynetwatch": {
      "command": "<node-or-package-runner>",
      "args": ["<energy-netwatch-mcp-server>"],
      "env": {
        "ENERGYNETWATCH_API_KEY": "<set locally>",
        "ENERGYNETWATCH_API_BASE_URL": "https://api.energynetwatch.com"
      }
    }
  }
}

Replace placeholders with the package helper output and local environment values.

Security boundary

The MCP server should call the public EnergyNetWatch API with X-API-Key. It should not receive RDS credentials, connect directly to the database, or print API keys during diagnostics.