# energyatit [Health: Active]

**Category:** 🏭 Industrial & IoT  
**Repository:** https://github.com/kasathur/energyatit-mcp-server  
**GitHub Stars:** 1  
**npm Downloads (last month):** 123  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/energyatit

## Description
Connect AI agents to energy infrastructure. Dispatch, attest carbon, read meters.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "energyatit": {
    "command": "npx",
    "args": ["-y","energyatit-mcp-server"],
    "env": {
      "ENERGYATIT_API_KEY": "",
      "ENERGYATIT_TOKEN": "",
      "ENERGYATIT_BASE_URL": ""
    }
  }
}
```

**Requires environment variables:** `ENERGYATIT_API_KEY`, `ENERGYATIT_TOKEN`, `ENERGYATIT_BASE_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the energyatit MCP server does

The energyatit MCP server gives AI agents an interface to energy sites, assets, meters, grid data, carbon records, settlements, and demand response workflows. Its tool set covers both operational queries and actions. Agents can list tenant sites, inspect BESS, HVAC, solar, and EV charger assets, read meters, check integration status, and run health checks.

Operational tools include dispatching commands to batteries, solar inverters, and EV chargers, viewing dispatch history, and creating, executing, and settling demand response events. The platform also exposes tools for reliability scoring at asset and site level, regional grid-capacity information, and real-time electricity prices.

## How it works

The package runs through the Model Context Protocol and can be started with `npx energyatit-mcp-server`. An MCP client launches the process and makes its tools available to an AI agent. Requests can use the EnergyAtIt platform through an API key or JWT token, while the sandbox provides simulated energy data without an API key.

The energyatit MCP server supports infrastructure and data workflows involving IEC 61850, DNP3, Modbus TCP/RTU, OpenADR 2.0b, OCPP 1.6/2.0, IEEE 2030.5, ICCP/TASE.2, and REST.

## Setup and configuration

Install and launch the server with:

```bash
npx energyatit-mcp-server
```

For Claude Desktop, add an `energyatit` entry that runs `npx` with `-y energyatit-mcp-server` and place credentials in the `env` object. Claude Code can add the server with:

```bash
claude mcp add energyatit -- npx -y energyatit-mcp-server
```

`ENERGYATIT_API_KEY` accepts an API key, while `ENERGYATIT_TOKEN` provides a JWT alternative. `ENERGYATIT_BASE_URL` changes the API base URL and defaults to `https://energyatit.com`.

## Tools and capabilities

The energyatit MCP server includes tools for:

- Listing sites and energy assets
- Reading meters and checking platform integrations
- Dispatching devices and reviewing command history
- Creating, dispatching, and settling demand response events
- Generating and verifying settlement and carbon hash chains
- Producing carbon certificates and Scope 2 or other compliance packages
- Scoring asset and site reliability
- Checking grid capacity and electricity prices
- Analyzing PPA, REC, and carbon-offset procurement
- Provisioning a sandbox and checking platform health

## Limitations and notes

Live platform access may require an API key or JWT, although sandbox use is available without an API key. Dispatch tools can send commands to supported energy devices, so agents should be given appropriate authorization and operational context before using them. The material lists supported protocols but does not specify device prerequisites, permission models, rate limits, or the exact response schema for each tool.

_Full upstream README: https://allmcps.com/mcp/energyatit/readme_