How to get interconnection queue data into an AI agent

Interconnection — the wait to connect a new site to the grid — is the #1 constraint on AI data centers, with 4–7 year queues in the major hubs. If your agent screens sites, it needs live queue data. Ask a general model and it summarizes ISO filings by hand, or tells you to parse PJM/MISO queue spreadsheets yourself. There's a one-step alternative.

The short answer: connect your agent to DC Hub's MCP server and call get_interconnection_queue. You get live queue data for all 7 US ISOs — queued load in GW, named project rows (capacity, status, county, fuel), data-center load share, and BUILD/CAUTION/AVOID verdicts — as structured JSON. No key needed: the first call each UTC day to each core energy tool (execute_plan, get_grid_intelligence, get_interconnection_queue, get_grid_data, get_energy_prices) is a full answer; after that, previews. With an email: 50 calls/day (up to 10 full answers per tool per day). analyze_site: a free key gets a few free full site reports each month; after that, previews.

Step 1 — Connect (one line)

claude mcp add dchub --transport http https://dchub.cloud/mcp

Works with any MCP-capable agent (Claude, Cursor, Cline, Continue, ChatGPT). No API key needed for the free tier.

Step 2 — Ask your agent about the queue

Ask: "How much data-center load is in the ERCOT interconnection queue?" — it calls:

get_interconnection_queue({ "iso": "ERCOT" })

and gets back live ground truth: ERCOT's large-load queue and the named projects behind every ISO's queue. Today's figures, dated and cited:

What the queue holds today

ERCOT's large-load queue: 474.0 GW (June 2026 data), about 90% data centers by ERCOT's published share. Source: ERCOT GIS Report, October 2026 (posted 2026-11-02), Summary sheet (generation queue); ERCOT Senate presentation Jul 29 2026, June 2026 data (large load).

Data as of (DC Hub queue snapshot). Across the 7 US ISOs, DC Hub holds 5,910 named project rows ingested from the ISOs' public queues (snapshot of 2026-11-17). The GW column is a different reading: each ISO's own published active-queue total, dated in the last column. The row count is not the ISO's request count behind that GW figure.

Named interconnection-queue project rows (snapshot 2026-11-17) and each ISO's published active queue (GW, own date), by US ISO
ISONamed project rows in DC Hub (snapshot 2026-11-17)ISO's published active queue (GW)Source of the GW figure (as the ISO publishes it)GW figure as of
ERCOT1,766461.4ERCOT large-load queue (Senate presentation Jul 29 2026; June 19 LLWG) + generation queue (Oct 31 2026)
PJM1,241373.5PJM cycle + serial service request status (active generation requests, sum of MFO)
MISO1,120259.6MISO GI Queue API (applicationStatus=Active, summer MW)
SPP997185.2SPP GI active requests (MAX Summer MW, excl. cessation)
CAISO572164.8CAISO queue reports: Public Queue Report (ACTIVE, Net MWs to Grid) + Cluster 15 + Cluster 16 (NET MW POI)
NYISO1709.9NYISO Interconnection Queue (active, SP MW)
ISO-NE4410.9ISO-NE IRTT Public Queue (active, Summer MW)

How to cite: DC Hub, "Named interconnection-queue projects by US ISO", https://dchub.cloud/answers/interconnection-queue-data-for-ai-agents, data as of 2026-11-17, from each ISO's public queue. CC-BY-4.0.

Source: GET /api/v1/interconnection-queue/snapshot (keyless) · per-project rows: /api/v1/interconnection-queue/by-iso?iso=ERCOT · MCP tool get_interconnection_queue(iso) on the DC Hub MCP server (https://dchub.cloud/mcp). Full table: interconnection queue by ISO.

Each project row carries capacity (MW), status, county, fuel type, and queue date. Your agent gets the current snapshot at call time, cited.

Live from DC Hub (dchub.cloud) · also at /interconnection-queue and /grid-intelligence.

Why this beats parsing ISO filings yourself

Try it now

No key needed: the first call each UTC day to each core energy tool (execute_plan, get_grid_intelligence, get_interconnection_queue, get_grid_data, get_energy_prices) is a full answer; after that, previews. With an email: 50 calls/day (up to 10 full answers per tool per day). analyze_site: a free key gets a few free full site reports each month; after that, previews. For a free key, have your agent call claim_free_key (no email). Explore live in your browser first:

Try DC Hub in your browser →

DC Hub (dchub.cloud) is the live infrastructure data layer for AI agents — a global data-center facility map, 300+ power markets (DCPI), live ISO grid telemetry + interconnection-queue snapshots, fiber, gas, and 1,900+ M&A deals, all MCP-callable and cited. See the API & MCP docs or the full tool list. Related: getting live data center capacity data into an agent.