WattIf MCP Servers

Energy intelligence for commercial and industrial buildings. Three MCP servers, each scoped to a different use case.

Servers

| Command | Package | For | Tools | |---|---|---|---| | wattif-monitor | Building operators | Status, queries, reports, schedules, device management | ~30 | | wattif-intelligence | Partners (ESCOs, REITs, engineers) | Context layers, waste analysis, benchmarks, forecasting, optimization | ~35 | | wattif-operate | Advanced operators (Orchestrate plan) | Cases, authority, service dispatch, settings, device control | ~30 | | wattif-platform | Internal / all tools | Everything above combined | ~95 |

Setup

1. Get an API key

Your WattIf admin will generate one for you via Loop:

"Generate an MCP key for [name] with read access"

2. Install

npm install -g wattif-platform

This installs all four commands.

3. Configure your AI client

Claude Desktop / Claude Code

Add to your MCP config (claude_desktop_config.json or .mcp.json):

{
  "mcpServers": {
    "wattif-monitor": {
      "command": "wattif-monitor",
      "env": {
        "WATTIF_API_KEY": "wif_pk_your_key_here"
      }
    }
  }
}

Replace wattif-monitor with wattif-intelligence or wattif-operate depending on your use case.

4. Use it

Start by selecting a facility:

"What facilities do I have access to?"

Then ask anything:

"Show me yesterday's load profile" "Are there any anomalies this week?" "What if we shifted HVAC start time to 6am?" "Run an optimization for tomorrow"

What each server does

wattif-monitor

For building operators who want to see what's happening and set up basic automation.

• Query real-time and historical energy data
• View anomalies and equipment status
• Create schedules and automations
• Generate energy reports
• Manage devices and assets

wattif-intelligence

For energy engineers, ESCOs, REITs, and design firms who need deep analytics.

• Six layers of context (patterns, correlations, benchmarks, equipment health)
• Waste analysis and drift detection
• Cost breakdown and forecasting
• Run MILP optimizations and what-if simulations
• Compare periods, assets, and portfolios

wattif-operate

For advanced operators on the Orchestrate plan who want AI-managed buildings.

• Create and manage cases (issue tracking with root cause)
• Configure authority levels (Sense/Think/Act)
• Dispatch technicians
• Full facility settings and configuration
• Send device commands
• Assessment and planning tools

API key scopes

Keys are scoped to control access:

| Scope | Access | |---|---| | read | Query data, baselines, anomalies, reports (default) | | write | Create/update schedules, automations, memories, assets | | control | Send device commands, run optimizations, configure authority |

Environment variables

| Variable | Required | Default | Description | |---|---|---|---| | WATTIF_API_KEY | Yes | - | Your API key (starts with wif_pk_) | | WATTIF_API_URL | No | https://wattif.ai | Platform URL (change for self-hosted) |

How it works

Each MCP server is a thin proxy. It fetches its scoped tools from the WattIf platform at startup, registers them as MCP tools, and forwards all execution to the platform API. Your data never leaves WattIf's infrastructure.

AI Client <--stdio--> MCP Server <--HTTPS--> WattIf Platform API

Self-hosted

Point to your instance:

{
  "env": {
    "WATTIF_API_URL": "https://your-wattif-instance.com",
    "WATTIF_API_KEY": "wif_pk_your_key_here"
  }
}

License

MIT