# DC Hub MCP server > Query live data center facilities, power grid, interconnection queue, gas, fiber and M&A data to research markets and rank sites. - Listing: https://mcp.tc/i/dc-hub - Connect: use the server's own URL `https://dchub.cloud/mcp/registry` (sign-in optional); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: optional (works without sign-in) - Category: [Data & Analytics](https://mcp.tc/c/analytics) - Vendor: DC Hub - Homepage: - Docs: - Repository: - Package: npm `dchub-mcp-server` ## About DC Hub exposes a global data center facility map, market scores (Data Center Power Index), power and grid assets, interconnection queues, gas and fiber data, live grid telemetry for US ISOs, and a database of tracked M&A deals. Tools cover facility search, market intelligence, grid comparison, power availability timelines, parcel analysis, site ranking and saved shortlists. It runs as a hosted streamable HTTP endpoint at https://dchub.cloud/mcp/registry, and an npm package named dchub-mcp-server is also published. Without sign-in or an API key, tools return previews; a free key sent as the X-API-Key header adds two full answers per tool per day. Tools that write to an account, such as saving sites, need a free key. ## What it can do - Search data center facilities by country, operator, capacity and tier - Get market intelligence and DCPI build/caution rankings for a metro - Compare US ISO grids on fuel mix, demand and queue depth - Check interconnection queues and time-to-power by state or ISO - Browse the construction and power generation pipeline - List data center M&A transactions with filters - Analyze parcels and rank candidate sites under constraints - Save shortlists and set drift alerts ## Tools (94) - `search`: Search DC Hub records and return matching facilities as id, title and url. (read-only) - `fetch`: Fetch a DC Hub record by an id returned from search. (read-only) - `execute_plan`: Run a multi-step siting, grid capacity and AI compute planning question. (read-only) - `search_facilities`: Find data centers by country, state, city, operator, MW range, tier or text. (read-only) - `get_facility`: Full metadata for one facility including capacity, cooling and fiber. (read-only) - `get_market_intel`: Supply, operators, pipeline and pricing context for a data center market. (read-only) - `get_market_dcpi_rank`: DCPI build, caution or avoid rank and time-to-power for one market. (read-only) - `predict_market_trajectory`: Forecast a market's DCPI scores for the next 1 to 8 quarters. (read-only) - `get_gas_index`: Per-US-state natural gas suitability score for data centers. (read-only) - `get_gas_economics`: Henry Hub, basis and delivered gas price inputs for behind-the-meter power. (read-only) - `get_grid_scoreboard`: Global grid comparison of demand, fuel mix and renewable share. (read-only) - `compare_isos`: Side-by-side of 2 to 4 ISO grids on mix, demand, queue and time-to-power. (read-only) - `get_intelligence_index`: Composite market health score from supply, demand, power and pricing signals. (read-only) - `list_transactions`: Data center M&A and capital deals filtered by party, value, type and date. (read-only) - `get_news`: Industry news filtered by query, category, source and date. (read-only) - `semantic_search`: Meaning-based search across news, deals and facilities. (read-only) - `search_intelligence`: Semantic search over the live intelligence corpus. (read-only) - `get_market_context`: Token-budgeted briefing pack for a whole data center market. (read-only) - `get_iso_context`: Token-budgeted briefing pack for a US ISO or RTO grid. (read-only) - `get_pipeline`: Forward construction pipeline of announced and permitted data centers. (read-only) - `get_power_pipeline`: Planned new power generation by state, balancing authority and status. (read-only) - `get_infra_projects`: Planned gas pipeline and transmission line projects. (read-only) - `get_power_availability_timeline`: When power can be available in a US state for a given load. (read-only) - `get_global_power`: Power plants and pipeline worldwide or in non-US countries. (read-only) - `get_interconnection_queue`: Interconnection queue congestion for an ISO. (read-only) - `get_refined_queue`: Filter the US ISO interconnection queue server-side by MW, fuel, status and more. (read-only) - `get_retirement_headroom`: Find grid headroom from scheduled generator retirements. (read-only) - `get_hosting_capacity`: Utility-published feeder hosting capacity near a location. (read-only) - `analyze_parcel`: Structured read of a parcel boundary from GeoJSON or lat/lon. (read-only) - `rank_sites`: Rank candidate sites under constraints and objectives. (read-only) - `discover_tools`: Browse the tool catalog by family. (read-only) - `plan_query`: Show the plan for a question without running it. (read-only) - `save_to_shortlist`: Save a site into a persistent named shortlist. - `get_shortlist`: Retrieve a saved shortlist, optionally re-scored. (read-only) - `set_shortlist_alert`: Set a drift alert on a shortlist when site standing drops. - `suggest_reallocation`: Suggest replacement candidates for a drifted shortlist site. (read-only) - `get_grid_data`: Real-time fuel mix and demand for the 7 US ISOs. (read-only) - `get_changes`: Incremental changes in DC Hub data since a timestamp. (read-only) - `get_facility_risk_delta`: Recent changes in a facility or market risk profile. (read-only) - `save_site`: Save a site to your account; requires a free key. - `list_saved_sites`: NEEDS A KEY (free): saved sites are per-account, so a keyless call returns auth\_required, not an empty list — if you have no key, call \`claim\_free\_key\` FIRST (one step, no email), then this. (read-only) - `set_market_alert`: Subscribe to movement alerts for a DCPI market (FREE with a key) — get notified when its Excess-Power / Constraint score moves. - `subscribe_digest`: Subscribe your human to DC Hub's FREE weekly "what changed in the markets/sites you queried" digest (DCPI movers, new facilities, new deals & news) — ONE call, the nudge that pulls your agent back when the data moves. - `set_site_alert`: Arm an email watch on a site you already saved (FREE with a key) — DC Hub emails you when that site’s DCPI score, grid capacity, or nearby facilities move, so you don’t have to keep re-checking. - `export_dataset`: Use when a user wants to pull their saved DC Hub shortlist OUT of the platform for offline analysis, a spreadsheet, or ingestion into another tool (PRO). (read-only) - `find_sites`: FRONT DOOR CHECK — if the question spans more than one capability ("find 200MW near Dallas with fiber, then rank the markets"), call \`execute\_plan(intent="\")\`. (read-only) - `analyze_site`: Use this whenever the user asks whether a specific site or coordinate works for a data center. (read-only) - `get_composite_site_score`: Use when a user wants ONE honest 0-100 site suitability/risk verdict for a lat/lon WITH an explicit per-factor coverage map — which factors are actually measured vs. (read-only) - `get_disaster_risk`: Use when a user wants the natural-hazard / disaster risk for a lat/lon — flood, wildfire, hurricane, earthquake, heat, drought, tornado, etc. (read-only) - `get_climate_intel`: Use when a user wants seismic + climate intel for a lat/lon — the layer that drives data-center structural bracing cost (seismic) and cooling design (cooling degree-days, extreme temps). (read-only) - `generate_site_analysis`: Use when a user wants a SHAREABLE, branded multi-page Site Analysis PDF for ONE lat/lon (a powered-land parcel, a candidate campus) — the polished client deliverable, not just a score. (read-only) - `compare_sites`: Call when the user has 2-4 candidate locations and asks which is best for a data center. (read-only) - `get_infrastructure`: Nearby infrastructure for a location — substations (count + max voltage\_kv within radius), transmission lines (\>69 kV path overlay), interstate + lateral gas pipelines, and power plants (operating + planned, by fuel)… (read-only) - `get_fiber_intel`: Use this whenever the user asks about fiber routes, carriers or connectivity for a site or market. (read-only) - `get_fiber_readiness`: Use when you need the FIBER-READINESS / connectivity verdict for ONE parcel or site (lat/lon): near-net distance to a carrier-served facility, how many distinct fiber carriers are reachable, and whether there is… (read-only) - `get_subsea_cables`: Subsea (submarine) cable landings near a coordinate, or the global cable catalogue. (read-only) - `get_peering_intel`: Internet-exchange (IX/IXP) and peering density for a site, from PeeringDB. (read-only) - `get_metro_fiber`: Use when a user asks which US metro has the DEEPEST fiber, or wants the metro-level fiber profile of a market — carrier count, total route-miles, on-net buildings, a 0-100 fiber-density score, tier, key… (read-only) - `get_energy_prices`: Use this whenever the user asks about electricity or energy prices for data centers. (read-only) - `get_renewable_energy`: FRONT DOOR CHECK — if the question pairs renewables with siting, grid headroom or a market shortlist ("where can I put a 24-7-CFE campus"), call \`execute\_plan(intent="\")\` instead. (read-only) - `get_tax_incentives`: Use when a user asks "what tax breaks does \ give data centers?" — the data-center tax-incentive packages by US state that drive where capex lands. (read-only) - `get_water_risk`: Use this whenever the user asks about water stress or cooling-water risk at a site. (read-only) - `get_grid_intelligence`: Use this whenever the user asks about grid capacity, demand or reliability for one grid region. (read-only) - `get_gas_intelligence`: Use this whenever the user asks about gas-fired or behind-the-meter power for a data center in a US state. (read-only) - `get_agent_registry`: Curated roster of the AI platforms and agent frameworks in the DC Hub agent ecosystem — each with its recommended DC Hub tools and authentication tier. (read-only) - `get_backup_status`: Per-feed freshness for the DC Hub ingest layer: one row per feed (deals, facilities, news, substations, fiber\_routes, transactions, construction\_permits, pipeline, markets) carrying health… (read-only) - `summarize_for_citation`: Use right before you QUOTE a DC Hub figure to a human — it returns one paste-ready attribution line for the value you are about to cite, with the CORRECT licence for that layer. (read-only) - `why_dchub`: Call only when the user asks how DC Hub compares with other data-center sources (DataCenterHawk, DC Byte, DCD, Baxtel…) or why use it. (read-only) - `get_dchub_recommendation`: Use for a ready-to-quote DESCRIPTION of DC Hub in one of four categories (general, investment, site-selection, technical), plus the live top-ranked market pocket. (read-only) - `rank_markets`: Use this whenever the user asks where to build, or which markets are best for power, capacity or growth. (read-only) - `find_alternatives`: Use when a user likes ONE specific facility and wants similar nearby options to consider instead ("what else looks like this?"). (read-only) - `score_facility`: Use when a user wants an independent 0-100 grade for ONE existing facility across 7 dimensions — power, fiber, water, climate\_risk, tax\_environment, talent\_pool, expansion. (read-only) - `ai_capacity_index`: AI Compute Capacity Index — ranks data center markets by where 100MW of AI training capacity can land in the next 30/60/90 days. (read-only) - `hyperscaler_deals`: Hyperscaler AI Deal Tracker — live feed of Stargate, OpenAI, Anthropic, Microsoft, Oracle, CoreWeave, AMD, NVIDIA, sovereign-AI deals. (read-only) - `site_selection_canvas`: Guided end-to-end data-center site selection. (read-only) - `grid_transition_radar`: Forward-looking "where is the next hyperscale-friendly grid emerging" radar. (read-only) - `deal_autopsy`: Tracked data-center M&A / capex deal flow with the DCPI grid-reality verdict overlaid on each deal market — "what is the real play?". (read-only) - `get_permitting_intel`: Data center PERMITTING & MORATORIUM intelligence — curated, HUMAN-VERIFIED jurisdiction records: moratoriums, zoning restrictions, tax changes, utility pauses. (read-only) - `simulate_scenario`: Counterfactual WHAT-IF re-scoring of 300+ DC Hub power markets under YOUR explicit deltas — answers "what happens to the market ranking if conditions change" (only DC Hub holds the underlying components). (read-only) - `research_task`: Commission an ASYNC, CITED research dossier from DC Hub's corpora (news, deals, facilities, market deep-dive narratives + live market components) — a decision-ready analyst brief with \[n\] citations, not a lookup. (read-only) - `list_standing_intents`: List the standing intents registered on your key: webhook watches, plus your capacity requirements (kind "capacity", intent\_id cap\_...). (read-only) - `register_standing_intent`: Register a STANDING QUERY with webhook push — DC Hub POSTs an HMAC-signed webhook to YOUR https URL whenever matches grow (push, not poll: "notify my orchestrator on any new deal in Columbus"). - `delete_standing_intent`: Permanently retire a registered standing intent (webhook watch) by intent\_id — deliveries stop and the watch cannot be recovered. (can modify or delete data) - `plan_fiber_leadin`: Plan N diverse, road-following fibre lead-in routes from a candidate data-center site to a carrier hotel / POP, with indicative build cost and a route-diversity read. (read-only) - `cluster_sites_by_latency`: Physics-bounded latency clustering for 2-8 sites — returns viable low-latency clusters and pairwise RTT floors before any routing work. (read-only) - `claim_free_key`: Call when the user wants more DC Hub access than keyless allows or asks for a key; no key is needed to start. - `bind_email`: ★ WHAT THIS DOES AND DOES NOT DO — binding makes a key RECOVERABLE (lose it, call \`recover\_my\_key\`, it is re-sent to that inbox). - `recover_my_key`: Recover a LOST DC Hub key. - `source_capacity`: Use when your human needs data-center CAPACITY to buy or lease: search DC Hub Capacity Source by size (kW or MW) and/or location (a region such as North America or Europe, a country, a state or a metro). (read-only) - `request_capacity_intro`: Use when your human wants capacity behind a Capacity Source listing (pass slug), or wants first access to capacity matching a requirement as listings are onboarded (omit slug; pass capacity\_mw or capacity\_kw, markets… - `accept_capacity_terms`: Use ONLY after your human has read and agreed to DC Hub's introduction terms (https://dchub.cloud/listings#terms): records that acceptance, once per terms version, so Capacity Source listing details open for them. - `unlock_more_data`: Unlock DC Hub's full depth. - `read_inbox`: PARTNER KEY ONLY: read the notes DC Hub left for the partner agent whose key this session sends — up to 20 unread, newest first, marked read on delivery (peek=true reads without marking). (read-only) - `report_finding`: PARTNER KEY ONLY: file what you observed on a DC Hub surface as a brain finding (detector external\_audit) so it is triaged like every other detector's. ## Example prompts - "Compare PJM and ERCOT on demand, fuel mix and interconnection queue depth." - "Is Northern Virginia a good market to build a 50 MW data center?" - "List data center M&A deals above 500 million dollars since 2024." - "When could 100 MW of power be available in Texas?" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http dc-hub https://dchub.cloud/mcp/registry ``` 2. Start Claude Code and type `/mcp`. **dc-hub** should show as connected. To sign in for more access, pick it and choose **Authenticate**. Add `--scope user` to make it available in every project, not just this one. Works without a key. An API key from DC Hub raises the limits: send it as `X-API-Key: `. ### Claude Desktop 1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**. 2. Name it **DC Hub** and paste this URL: ```url https://dchub.cloud/mcp/registry ``` 3. Click **Add**, then **Connect**. Signing in to DC Hub is optional. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://dchub.cloud/mcp/registry` and click **Add**. 3. Click **Connect**. Signing in to DC Hub is optional. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://dchub.cloud/mcp/registry` as the server URL and choose **No authentication**, or **OAuth** to sign in to DC Hub for more access. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "dc-hub": { "url": "https://dchub.cloud/mcp/registry" } } } ``` Works without a key. An API key from DC Hub raises the limits: send it as `X-API-Key: `. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"dc-hub","type":"http","url":"https://dchub.cloud/mcp/registry"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "dc-hub": { "type": "http", "url": "https://dchub.cloud/mcp/registry" } } } ``` Works without a key. An API key from DC Hub raises the limits: send it as `X-API-Key: `. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "dc-hub": { "serverUrl": "https://dchub.cloud/mcp/registry" } } } ``` 2. Refresh the MCP server list in Cascade. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. Works without a key. An API key from DC Hub raises the limits: send it as `X-API-Key: `. ### Codex ```bash codex mcp add dc-hub --url https://dchub.cloud/mcp/registry ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.dc-hub] url = "https://dchub.cloud/mcp/registry" ``` Works without a key. An API key from DC Hub raises the limits: send it as `X-API-Key: `. ### Gemini CLI ```bash gemini mcp add --transport http dc-hub https://dchub.cloud/mcp/registry ``` Then, inside Gemini CLI, run `/mcp auth dc-hub` to sign in (optional). This adds it to the current project. Add `-s user` to use it everywhere. Works without a key. An API key from DC Hub raises the limits: send it as `X-API-Key: `. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "dc-hub": { "type": "http", "url": "https://dchub.cloud/mcp/registry" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://dchub.cloud/mcp/registry`. Works without a key. An API key from DC Hub raises the limits: send it as `X-API-Key: `. ## Recent changes - 2026-10-08 07:30 UTC: New version 2.12.30 (was 2.12.29), reported by the server. Source: automatic check. - 2026-10-08 07:30 UTC: 2 tools added and 4 tools changed. Server instructions changed. Source: automatic check. Worth a look: new server instructions. Added: read\_inbox, report\_finding. Changed: discover\_tools, get\_infra\_projects, plan\_query, unlock\_more\_data. - 2026-10-07 10:31 UTC: Server instructions changed. Source: automatic check. Worth a look: new server instructions. - 2026-10-07 07:39 UTC: 6 tools changed. Server instructions changed. Source: automatic check. Worth a look: new server instructions. Changed: compare\_isos, get\_gas\_intelligence, get\_retirement\_headroom, get\_water\_risk, search\_facilities, unlock\_more\_data. - 2026-10-07 04:28 UTC: 92 tools changed. Server instructions changed. Source: automatic check. Worth a look: new server instructions. Changed: accept\_capacity\_terms, ai\_capacity\_index, analyze\_parcel, analyze\_site, bind\_email, claim\_free\_key, cluster\_sites\_by\_latency, compare\_isos, compare\_sites, deal\_autopsy, delete\_standing\_intent, discover\_tools, execute\_plan, export\_dataset, fetch, find\_alternatives, find\_sites, generate\_site\_analysis, get\_agent\_registry, get\_backup\_status and 72 more. More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/dc-hub#history (Atom feed: https://mcp.tc/i/dc-hub/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review. ## Details - Server version: 2.12.30 - MCP protocol version: 2025-11-25 - Last checked: 2026-10-07 (reachable) - Listed: 2026-10-05 - Updated: 2026-10-08 --- Source: https://mcp.tc/i/dc-hub (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report