Getting Started
Query Atlas data from Claude, ChatGPT, Copilot, or any MCP client. Grid, flow and forecast-score tools work on every plan; Pro adds siting and capacity tools; Growth adds Power Grid search.
A hosted Model Context Protocol server. Your assistant reads live and 15-minute state demand, fuel mix, IEX prices, inter-state flows and forecasts. Pro keys add site screens, hosting capacity and substation capacity. Growth keys search substations, lines and plants on the Power Grid map, including modelled line loading.
| Aspect | Details |
|---|---|
| Endpoint | https://api.energymap.in/mcp |
| No-key endpoint | https://api.energymap.in/mcp/public, 19 public tools |
| Transport | Streamable HTTP (stateless) |
| Auth | API key — X-API-Key or Authorization: Bearer header, or ?api_key= in the URL |
| Included with | Every plan, at its API limits (see pricing) |
| Tools | 26, all read-only |
| Metering | Calls share the key's REST quotas |
Free public connector documentation
https://api.energymap.in/mcp?api_key=iea_live_YOUR_KEY. The connector UI has no custom-header field, so the key rides in the URL here.claude mcp add --transport http energy-atlas https://api.energymap.in/mcp \
--header "X-API-Key: iea_live_YOUR_KEY"{
"mcp_servers": [
{
"type": "url",
"url": "https://api.energymap.in/mcp",
"name": "energy-atlas",
"authorization_token": "iea_live_YOUR_KEY"
}
]
}https://api.energymap.in/mcp?api_key=iea_live_YOUR_KEY and authentication set to none (the key is in the URL).Prefer headers where the client supports them
Keys in URLs can end up in logs and screenshots. Claude Code, the Claude API and every Copilot client support header auth. Use it there. The URL form exists for connector UIs that cannot set headers.
Builds a Copilot agent that you can publish to Microsoft 365 Copilot, Teams or a website. Generative orchestration must be on for the agent.
https://api.energymap.in/mcp.X-API-Key. Select Create.For the 19 no-key tools, use https://api.energymap.in/mcp/public with authentication set to None. Each person who uses a published agent with the keyed URL is asked for their own key on first use.
Save as .vscode/mcp.json in a workspace, or run MCP: Open User Configuration for every workspace. VS Code asks for the key once and stores it encrypted. Then pick Agent mode in Copilot Chat.
{
"inputs": [
{ "id": "atlas-key", "type": "promptString", "password": true, "description": "Atlas API key" }
],
"servers": {
"energy-atlas": {
"type": "http",
"url": "https://api.energymap.in/mcp",
"headers": { "X-API-Key": "${input:atlas-key}" }
}
}
}copilot mcp add --transport http \
--header "X-API-Key: iea_live_YOUR_KEY" \
energy-atlas https://api.energymap.in/mcp.mcp.json at the solution root.COPILOT_MCP_ATLAS_KEY in the copilot environment.| Tool | Returns | Arguments | Plans |
|---|---|---|---|
live_demand | Latest demand snapshot: every state plus the All-India aggregate | state (optional slug) | Every plan |
state_snapshot | Latest demand, peak, and frequency for one state | state (required slug) | Every plan |
state_demand_15min | One state's continuous 15-minute demand, every block labelled actual or estimate | state (required slug), hours or from_date and to_date | Every plan, window capped by plan history |
fuel_mix | Hourly generation by fuel — national, or one state's breakdown | state (optional), hours (default 48) | Every plan |
iex_prices | Latest IEX market clearings (DAM, RTM, GDAM) | market (optional), hours (optional) | Every plan |
demand_forecast | Hourly demand forecast with p10/p50/p90 bands and daily peaks | state (optional), horizon (default 24, max 48) | Growth+ |
search_datasets | The Atlas dataset catalogue with freshness and provenance | query (optional text filter) | Every plan, unmetered |
data_centre_site_screen | Bounded Data Centre development screen for one India coordinate | latitude, longitude, label (optional) | Pro+ |
data_centre_compare_sites | Ranked comparison of two to five evidence-aware site screens | sites (2–5 labels and coordinates) | Pro+ |
data_centre_delivered_cost | Indicative annual power-cost range from published charges and user assumptions | site, IT load, PUE, load factor, demand charge, adders, losses | Pro+ |
data_centre_evidence_receipt | Component availability, provenance detail, tariff freshness, confidence, and boundary | latitude, longitude, label (optional) | Pro+ |
data_centre_development_bands | Coarse 0.5-degree count and severity bands without raw tracker records | limit (1–500) | Pro+ |
substation_capacity | Capacity for a new load at one studied substation, or at the studied substations nearest a point | substation_id, or latitude and longitude (max_km, limit optional) | Pro+ |
site_withdrawal_check | Whether a new load of the given MW can connect firm near a point, ranked across studied substations | latitude, longitude, mw (max_km, limit optional) | Pro+ |
power_grid_search | Substations, lines and plants: by name, near a place, in a district or radius, by voltage, fuel, headroom or modelled line loading | asset, state, and name, near, district or coordinates | Growth+ |
hosting_capacity | Injection MW, band and binding branch from the national DC power flow screen | latitude and longitude, or substation_id | Pro+ |
district_grid_topology | District 66 kV+ network: feeds, radial stations, single points of failure | district (Rajkot, Porbandar), station, min_kv | Pro+ |
district_injection_headroom | Indicative N-0 and N-1 line headroom for a new injection at each district station | district, mw, station (optional) | Pro+ |
interstate_power_flows | Each state's net import or export, drawal, schedule and deviation | state (optional), hours (1–168) | Every plan |
iex_dam_forecast | DAM price outlook to D+30, or the next-day 96-block curve | view, delivery_date (optional) | Starter+ |
iex_forecast_scorecard | How the price forecast has scored against a naive guess | market (DAM or RTM) | Every plan |
iex_rtm_forecast | Next 8 RTM blocks, p10 to p90, a shadow forecast | as_of (optional) | Growth+ |
forecast_vintage | One delivery day's forecast exactly as published at a time | market, delivery_date, as_of | Growth+ |
forecast_scores | Forecast MAE, skill and coverage per day or rolling window | market, window or dates | Every plan |
grid_events | Price-cap days, demand records, outages and frequency excursions | type, state, dates, q (all optional) | Every plan |
my_grid_context | Your own watches, projects, changes and alerts | window (7d or 30d) | Pro+ |
Large responses are truncated to 50 list items with a truncated: true marker. Every metered response carries the same meta block as the REST API, so the assistant can report remaining quota and data provenance.
The connector uses your ordinary Atlas API keys — the same ones that call /developer/v1. Create and revoke them at Settings → API Keys. Key format, rotation, and IP allow-lists work exactly as described in Authentication.
Installing a connector needs no key — initialize and tools/list are open. The key is required per tool call; a key-less call returns an instruction naming this page instead of data.
Every tool call debits the key's daily and per-minute counters, the same as a REST call. Siting tools need Pro or above; substation capacity shows the MW figure on Enterprise and the band on other plans. Power Grid search needs Growth or Enterprise. Prices are on the pricing page.
| Plan | Core connector | Siting tools | Power Grid search | Calls per day (shared) | Calls per minute |
|---|---|---|---|---|---|
| Sandbox | Included | — | — | 100 | 3 |
| Student | Included | — | — | 100 | 10 |
| Institutional | Included | — | — | 5,000 | 30 |
| Grid AI | Included | — | — | 100 | 3 |
| Pro | Included | Included | — | 100 | 10 |
| Starter | Included | Included | — | 10,000 | 60 |
| Growth | Included | Included | Included | 100,000 | 300 |
| Enterprise | Included | Included | Included | Unlimited | 600 |
Dataset gates apply unchanged: demand_forecast follows the forecast-family gate (Growth and above), and keys on plans without it get a plain upgrade message from the tool. State-level access follows the same per-plan gate as REST. The other metered tools work on every plan.
| Tool error | Meaning | Fix |
|---|---|---|
api_key_missing | No key reached the server | Add the key as a header or ?api_key= in the connector URL |
api_key_invalid | Key unknown, revoked, or expired | Check Settings → API Keys and paste a live key |
plan_does_not_include_mcp | MCP was explicitly disabled for this plan — every standard plan includes it | Contact support if you see this on a standard plan |
not_in_plan | The dataset is gated above the key's plan | See the pricing page for plans that include it |
quota_exceeded | Daily quota or per-minute rate limit reached | Wait for the window to reset, or upgrade |
atlas_pro_required | A Data Centre workflow tool was called with a plan below Atlas Pro | Upgrade to Pro or use the public single-site screening tools |
plan_verification_unavailable | The server could not verify Pro access and failed closed | Retry shortly; protected tools never fall back to public access |
upstream_error | The Atlas API returned an unexpected error | Retry; if it persists, contact support |
curl -X POST https://api.energymap.in/mcp with an initialize JSON-RPC body returns the server info.