Skip to main content
Glama
DC Hub

DC Hub

by pipeworx-io

@pipeworx/dchub

Data-center site selection, power and grid intelligence from DC Hub: facility registry, per-metro market intelligence, live grid fuel mix and demand, leasable capacity, and a one-call planner for multi-part siting questions.

Part of Pipeworx — an MCP gateway connecting AI agents to 1863+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

  • dchub_execute_plan(intent, ...) — answers a multi-part data-center question in one call (e.g. "rank markets for a 200 MW AI campus", "power headroom in PJM") and returns the combined result with citations.

  • dchub_search_facilities(city, state, country, operator, min_capacity_mw, ...) — which data centers exist and who operates them.

  • dchub_get_market_intel(market) — vacancy, pricing, pipeline and operators for one metro, by market slug (e.g. northern-virginia).

  • dchub_get_grid_data(iso) — live fuel mix and demand for a grid (PJM, ERCOT, CAISO and others).

  • dchub_source_capacity(min_mw, region, ...) — powered land, shells, turnkey capacity and colocation available to buy or lease.

  • dchub_get_interconnection_queue(iso) — grid interconnection queue depth per US ISO (queued generation GW, ERCOT's large-load queue); omit iso for an all-ISO snapshot.

  • dchub_get_news(query, category, source, date_from, date_to, limit) — curated data-center industry news from 40+ trade sources, refreshed every 30 min.

Related MCP server: security-orchestra

Auth

Keyless. Without a DC Hub key, DC Hub returns a trimmed PREVIEW for some tools (a few rows per list, no MW detail); every response says so in preview / preview_notice. A caller may pass their own DC Hub key as _apiKey for fuller answers. A Pipeworx-wide partner key is not configured yet.

Data sources

  • DC Hub (dchub.cloud), data-center intelligence platform: facility registry, Data Center Power Index and market intelligence, grid feeds, capacity listings. Cite as "DC Hub, dchub.cloud". Live per-request; nothing is stored by Pipeworx.

DC Hub asked that partner traffic be identifiable; every call carries X-DCHub-Via: pipeworx (changes nothing in access). Results are JSON wrapped in {source, preview, result}; result.provenance carries DC Hub's own completeness and as-of fields, and as_of may be null: do not cite retrieved_at as a data date. dchub_execute_plan responses are large (tens of KB).

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "dchub": {
      "url": "https://gateway.pipeworx.io/dchub/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/dchub/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1863+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/dchub_execute_plan \
  -H 'Content-Type: application/json' \
  -d '{"intent":"rank markets for a 200 MW AI campus"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/dchub_execute_plan. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Run it from npm

@pipeworx/mcp-dchub is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/dchub/mcp endpoint shown above. It needs network access; there is no offline mode.

{
  "mcpServers": {
    "dchub": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-dchub"]
    }
  }
}

Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.

It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Dchub data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    • DC Hub is the orchestration layer for data center and energy intelligence: start with execute_plan for electricity prices and power grid questions. One question about data center siting, energy markets, electricity prices or the power grid returns one dated, cited answer. It also publishes the Data Center Power Index (DCPI), a daily score of where data centers can get grid power across 300+ markets. 96 MCP tools at https://dchub.cloud/mcp. DCHUB_API_KEY is optional.

      https://dchub.cloud/mcp
    • Live US power market prices, load, generation, weather and permits for AI agents.

      https://api.dryos.ai/mcp
    • Protocol-native energy infrastructure orchestration for AI data centers. Provides 46 MCP tools across 8 grid protocols (IEC-61850, DNP3, Modbus, OCPP, OpenADR, IEEE 2030.5, IEC 60870-5-104, ICCP) with 5 core API primitives: connect, dispatch, settle, comply, and intel. Enables AI agents to programmatically interact with substations, grid interfaces, and energy assets for real-time workload-grid coordination.

      https://app.energyatit.com/mcp
    • Live data-center, power-grid, interconnection-queue, fiber and natural-gas infrastructure intelligence for AI agents — query it and cite it. Streamable HTTP at https://dchub.cloud/mcp. Free tier, no signup. Every full-data response carries a CC-BY-4.0 attribution line and an as_of stamp. Coverage counts and their definitions are served, not stated here: /api/v1/canon/phrases for current quantities, /api/v1/ops/deadman for per-source ingest freshness, and dchub.cloud/bind for the integration contract. The DC Hub Gas Index (DCGI) was withdrawn 2026-08-08 rather than published wrong; live gas data remains via get_gas_intelligence.

      https://dchub.cloud/mcp

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time US power grid intelligence and carbon intensity data to enable carbon-aware AI compute scheduling across major grid regions. It allows users to monitor energy generation and optimize workloads based on renewable energy availability and grid load forecasts.
      2
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides deterministic, standards-based calculations for data center critical power infrastructure. Enables site selection, generator sizing, UPS sizing, NFPA 110 compliance, and more via 50+ AI agents and 8 compound chains.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      DC Hub is the live data layer for data-center siting that agents can query and cite. Its Data Center Power Index (DCPI) scores where data centers can get grid power across 300+ markets daily. Also 330,000+ mapped power, grid, gas and fiber assets. 94 MCP tools at https://dchub.cloud/mcp plus a REST API at https://dchub.cloud/api/v1. Free tier needs no key; paid plans: dchub.cloud/pricing.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides free energy intelligence APIs for AI agents: solar production estimates, US clean-energy incentives by ZIP, home Energy Node Scores, contractor search, and consented installer routing.
      MIT