Atlas Pro — 1-yr history, chart & CSV exports, new features, daily brief, MCP connector
— ₹399/mo.Atlas Pro — 1-yr history, chart & CSV exports, new features, daily brief, MCP connector
— ₹399/mo.
DocsGetting Started
Query Atlas data from Claude, ChatGPT, or any MCP client. Six metered grid tools are included with every plan; Atlas Pro and above add five Data Centre workflow tools.
The Energy Atlas MCP connector is a hosted Model Context Protocol server. Point an assistant at it and the assistant can pull live demand, fuel mix, IEX prices, demand forecasts, and the dataset catalogue directly from the Atlas. Atlas Pro keys can also screen and compare Data Centre sites, model delivered electricity cost, assemble evidence receipts, and inspect coarse development-signal bands.
| Aspect | Details |
|---|---|
| Endpoint | https://api.energymap.in/mcp |
| Transport | Streamable HTTP (stateless) |
| Auth | API key — X-API-Key or Authorization: Bearer header, or ?api_key= in the URL |
| Included with | Six core tools on every plan; five Data Centre tools on Pro and above (see pricing) |
| Tools | 11, all read-only; 5 require Atlas Pro or above |
| Metering | Core data calls share REST quotas; Data Centre workflow tools are plan-gated |
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 and the Claude API support header auth — use it there. The URL form exists for connector UIs that cannot set headers.
| Tool | Returns | Arguments | Metered |
|---|---|---|---|
live_demand | Latest demand snapshot: every state plus the All-India aggregate | state (optional slug) | Yes |
state_snapshot | Latest demand, peak, and frequency for one state | state (required slug) | Yes |
fuel_mix | Hourly generation by fuel — national, or one state's breakdown | state (optional), hours (default 48) | Yes |
iex_prices | Latest IEX market clearings (DAM, RTM, GDAM) | market (optional), hours (optional) | Yes |
demand_forecast | Hourly demand forecast with p10/p50/p90 bands and daily peaks | state (optional), horizon (default 24, max 48) | Yes |
search_datasets | The Atlas dataset catalogue with freshness and provenance | query (optional text filter) | No |
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+ |
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.
The six core data tools debit the same daily and per-minute counters as REST calls on the key. The five Data Centre workflow tools are available only to Pro, Starter, Growth and Enterprise keys and return bounded derived results. Prices are on the pricing page.
| Plan | Core connector | Data Centre tools | Calls per day (shared) | Calls per minute |
|---|---|---|---|---|
| Sandbox | Included | — | 100 | 3 |
| Student | Included | — | 1,000 | 20 |
| Institutional | Included | — | 5,000 | 30 |
| Grid AI | Included | — | 100 | 3 |
| Pro | Included | Included | 100 | 10 |
| Starter | Included | Included | 10,000 | 60 |
| Growth | Included | Included | 100,000 | 300 |
| Enterprise | 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.