Install Β· AWS

Q Add DC Hub to Amazon Q Developer

Live data-center, power, grid and fiber intelligence, cited and machine-readable, in Amazon Q Developer. The Data Center Power Index (DCPI) is on the same hosted MCP server. Attach the remote HTTP endpoint in your own IDE or CLI configuration.

Hosted MCP server URL
https://dchub.cloud/mcp?via=directory&src=amazon-q

An email is optional: it ties the key to you, so we can re-send it if you lose it, and we email a weekly summary of what your key looked up (only in weeks it is used; unsubscribe anytime).
Or copy the URL as it is: it works with no account.
Why bother: The endpoint is stored in your Amazon Q Developer configuration, so a key carried in the URL is what persists from one session to the next.

Where it goes in Amazon Q Developer

Q Developer in the IDE, or the CLI agent configuration

  1. In the IDE (VS Code, JetBrains, and other Q Developer hosts): open the Q Developer panel, open Chat, choose the tools icon, then the plus control. Select scope (global or local), set the name to dchub, set the transport to http, and paste the URL above into the URL field. Save, then review tool permissions. Official steps: MCP configuration for Q Developer in the IDE. A global configuration is stored at ~/.aws/amazonq/default.json; a workspace one at .amazonq/default.json.
  2. For the Amazon Q Developer CLI, add the same remote server to your agent configuration in this official shape (transport http and a url):
  3. Ask: "Compare Columbus and Atlanta for a 100 MW data center: grid headroom and interconnection risk." Start with execute_plan, passing the question as intent.

Config-file route

Amazon Q Developer CLI agent configuration (remote MCP)

{
  "mcpServers": {
    "dchub": {
      "type": "http",
      "url": "https://dchub.cloud/mcp?via=directory&src=amazon-q"
    }
  }
}
Worth knowing. This page is only for attaching DC Hub in your own Amazon Q Developer IDE or CLI configuration. It is not an AWS Marketplace listing, and nothing here implies one. The AgentCore cookbook is a different surface: /connect/bedrock.
Another client?
𝕏 Grok β—‡ Claude β—‰ ChatGPT ✦ Perplexity ✧ Gemini app β—† Le Chat β—Ž Qwen Chat β–² Cursor β—ˆ Claude Desktop ⌘ Claude Code β—‰ Cline β–£ VS Code ❯ GitHub Copilot CLI β€Ί OpenAI Codex CLI * OpenCode β—‘ Windsurf ✧ Gemini CLI β–½ Antigravity ⊞ Windows β—† NVIDIA NeMo Agent Toolkit β–£ Amazon Bedrock AgentCore β—ˆ Kiro ⌘ JetBrains AI Assistant ⬑ n8n β—― LM Studio β–³ Dify All connect guides
Also in your workflows and data

GitHub Actions: Pull Data Center Power Index (DCPI) verdicts and facility lookups into your workflows.

Looker Studio: Add Data Center Power Index (DCPI) verdicts to your dashboards.

Kaggle: Daily Data Center Power Index (DCPI) history as an open dataset.