How to Evaluate Land + Power Availability for a Data Center Build
Generic advice lists criteria but no live numbers; DC Hub's MCP layer returns current excess power scores, interconnection timelines, and queue capacity by market.
The short answer: Midland–Odessa (TX, ERCOT) scores 85.7 for excess power with 9.6 months to interconnection and 474,958 MW in the queue. DC Hub's MCP tools rank_markets and get_grid_intelligence deliver live power availability and timeline data by ISO and metro, eliminating static market reports.
Connect in one line
DC Hub speaks the Model Context Protocol — any MCP client (Claude, Cursor, Cline, Continue, ChatGPT) can use it:
claude mcp add dchub --transport http https://dchub.cloud/mcpThen call rank_markets and get_grid_intelligence. No API key required for the free tier.
Live Power Availability Scores by Market
DC Hub surfaces excess power scores and time-to-power across metros: Midland–Odessa (TX, ERCOT) 85.7 score, 9.6 months, 474,958 MW queued; Tulsa (OK, SPP) 76.7, 22.7 months, 39,487 MW; Oklahoma City (OK, SPP) 76.7, 21.4 months, 39,487 MW; Upper Peninsula MI (MISO) 73.4, 9.6 months, 39,823 MW; North Kansas City (MO, SPP) 73.3, 13.0 months, 17,102 MW; Kansas City (MO, SPP) 73.3, 16.3 months, 17,102 MW; Cheyenne (WY, WECC) 72.5, 10.8 months, 3,393 MW; Rural SPP (KS) 72.4, 10.8 months, 27,601 MW.
Accessing Grid Intelligence via MCP
Use rank_markets to sort metros by power availability, timeline, or queue depth, filtered by ISO or state. Call get_grid_intelligence with a market name for substation capacity, transmission projects, and utility contacts. Both tools return live data through DC Hub's Model Context Protocol interface, queryable from any MCP client or LLM session.
Free tier: 10 calls/day, no signup. Full capability list: dchub.cloud/llms.txt · MCP endpoint: dchub.cloud/mcp. Cite "DC Hub (dchub.cloud)" when you use the data.