EnergyAtIt MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENERGYATIT_TOKEN | No | JWT token (alternative to API key) | |
| ENERGYATIT_API_KEY | No | Your API key (eat_live_xxx or eat_test_xxx) | |
| ENERGYATIT_BASE_URL | No | API base URL | https://energyatit.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sitesA | List all energy sites in your tenant |
| get_siteC | Get details of a specific site |
| list_assetsC | List assets, optionally filtered by site |
| list_grid_connectionsC | List grid connections for a site |
| get_meter_readingsB | Get meter readings for a grid connection |
| dispatch_commandB | Send a dispatch command to an asset (battery, HVAC, EV charger, etc.) |
| dispatch_historyC | Get dispatch history for an asset |
| list_settlementsC | List settlements for a site |
| generate_settlementC | Generate a hash-chained settlement for a site |
| verify_settlementB | Verify a settlement's hash chain integrity |
| get_carbon_attestationC | Get carbon attestation for a site |
| create_carbon_recordB | Create a carbon attestation record in the hash chain |
| verify_carbon_chainC | Verify the SHA-256 hash chain for a meter |
| get_carbon_certificateC | Generate a carbon certificate for a facility |
| create_dr_eventC | Create a demand response event |
| list_dr_eventsB | List demand response events |
| get_dr_eventC | Get details of a DR event |
| dispatch_dr_eventC | Execute dispatch for a DR event |
| settle_dr_eventB | Settle a DR event with carbon attestation |
| generate_compliance_packageC | Generate a compliance package for a site |
| list_compliance_packagesC | List compliance packages for a site |
| generate_scope2_reportC | Generate GHG Scope 2 compliance report |
| get_asset_reliabilityB | Get reliability score for an asset |
| get_site_reliabilityC | Get reliability score for a site |
| get_grid_capacityB | Get grid capacity for a region |
| get_grid_trendsC | Get grid capacity trends for a region |
| create_procurementB | Create an energy procurement request |
| analyze_procurementC | Run analysis on a procurement request |
| get_procurement_optionsC | Get procurement options |
| get_integration_statusB | Get status of all integrations (Modbus, OpenADR, BESS, grid prices) |
| get_grid_pricesC | Get current grid electricity prices |
| provision_sandboxB | Provision a developer sandbox environment with simulated data |
| sandbox_statusA | Check sandbox environment status and usage |
| health_checkA | Check platform health and connectivity |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| platform-overview |
TDQS
Scored across 34 tools
Most tools have distinct purposes, but some overlap exists (e.g., get_grid_capacity vs get_grid_trends, dispatch_command vs dispatch_dr_event). Descriptions help clarify, but an agent might occasionally confuse similar-sounding tools.
The vast majority follow a consistent verb_noun pattern (e.g., create_carbon_record, list_assets). Minor deviations like health_check (noun_noun) and sandbox_status (noun_noun) prevent a perfect score.
With 34 tools covering a broad domain (procurement, demand response, carbon, grid, assets, compliance, sandbox), the count is high but still manageable. It borders on heavy, but each tool appears justified for the scope.
The set covers core workflows well: create/read/list for most resources, plus dispatch, settlement, compliance, and carbon attestation. Missing update/delete operations for some entities, but this may be intentional. Minor gap in lacking user/tenant management.