Repository navigation
Add DC Hub MCP - #383
Add DC Hub MCP#383azmartone67 wants to merge 7 commits into
Conversation
|
Friendly follow-up on this one. The entry is still current: DC Hub is a hosted remote MCP server at https://dchub.cloud/mcp (94 tools, free tier needs no key). Happy to adjust wording, section or format if anything should change. Thanks for maintaining the list! |
|
Hi, a quick follow-up on this one. DC Hub's hosted endpoint (https://dchub.cloud/mcp, Streamable HTTP, no key needed for the free tier) is live on v2.12.45 with 94 tools. Happy to change the section or wording if anything doesn't fit. Thanks for maintaining the list! |
| @@ -0,0 +1,30 @@ | |||
| id: dc-hub | |||
| name: DC Hub | |||
| description: DC Hub is the orchestration layer for data center and energy intelligence: start with execute_plan. Its Data Center Power Index (DCPI) is a daily | |||
There was a problem hiding this comment.
CRITICAL: The unquoted : in this plain scalar makes MCP.yaml invalid YAML, so bin/generate-mcps-marketplace.ts cannot parse this entry.
Trigger: YAML plain scalars may not contain a colon followed by a space, and this value contains ... intelligence: start with execute_plan. .... yaml.parse() raises a parse error at that colon, which fails the Generate Marketplace workflow (pnpm exec tsx generate-mcps-marketplace.ts) for the whole catalog, not just this entry.
Impact: mcps/marketplace.yaml is committed with the same unquoted value at line 1295, so the published MCP catalog would be unparsable for consumers too.
Minimal fix: double-quote the whole description, as mcps/transform-mcp/MCP.yaml does for its colon-containing description, or rephrase to remove the colon (for example ... energy intelligence. Start with the execute_plan tool.). Then regenerate mcps/marketplace.yaml with the generator instead of editing it by hand. The same text at mcps/marketplace.yaml:1295 needs the same correction.
| placeholder: cloud.getdbt.com | ||
| - id: dc-hub | ||
| name: DC Hub | ||
| description: DC Hub is the orchestration layer for data center and energy intelligence: start with execute_plan. Its Data Center Power Index (DCPI) is a daily |
There was a problem hiding this comment.
SUGGESTION: The description is written partly as an imperative instruction to the agent (start with execute_plan) and cites the internal parameter key (DCHUB_API_KEY is optional).
Marketplace descriptions are presented to users and surfaced to agents, so imperative tool directives read as behavior instructions rather than capability descriptions. Prefer describing what the server provides, and keep install/parameter detail in the content and parameters fields. Fix this in mcps/dc-hub/MCP.yaml and regenerate, since this file is generated output.
Code Review SummaryStatus: 1 Issue Found | Recommendation: Merge (suggestion only) Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (2 files)
VerificationVerified at HEAD Unverified: the new "read-only" claim and the "dated, cited answer" behavior. Commit Fix these issues in Kilo Cloud Previous Review Summaries (3 snapshots, latest commit 19d315b)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 19d315b)Status: 1 Issue Found | Recommendation: Merge (suggestion only) Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (2 files)
Verified / UnverifiedVerified from the repository: the previous CRITICAL is fixed. Note: the generated Unverified: the rewritten endpoint URLs Fix these issues in Kilo Cloud Previous review (commit d4733ca)Status: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)CRITICAL
SUGGESTION
Files Reviewed (2 files)
Verified / UnverifiedVerified from the repository: the incremental commit Unverified: the actual live tool count (now 97 in the description vs 94 in the PR body and 96 before this commit), the hosted endpoint Fix these issues in Kilo Cloud Previous review (commit 996a29e)Status: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)CRITICAL
SUGGESTION
Files Reviewed (2 files)
Verified / UnverifiedVerified from the repository: directory/ Unverified: the hosted endpoint Reviewed by deepseek-v4.1-flash-1017 · Input: 46K · Output: 14.6K · Cached: 805K Review guidance: REVIEW.md from base branch |
Live server is now 2.12.59 with 97 tools (request_enhancement added). Canonical endpoint remains https://dchub.cloud/mcp.
| placeholder: cloud.getdbt.com | ||
| - id: dc-hub | ||
| name: DC Hub | ||
| description: "DC Hub: the orchestration layer for data center and energy intelligence. One read-only server for facilities, colocation, power and grid, interconnection queues, electricity and gas prices, fiber and site selection, including the Data Center Power Index (DCPI). Its execute_plan tool chains the right tools into one dated, cited answer. Works without an API key; a key is optional." |
There was a problem hiding this comment.
SUGGESTION: This generated entry is not reproducible with bin/generate-mcps-marketplace.ts, so the Generate Marketplace workflow will rewrite it.
Trigger: bin/marketplace-generator-utils.ts:102 dumps with lineWidth: 120, which folds long quoted scalars - see mcps/transform-mcp/MCP.yaml:3 producing the wrapped two-line entry at mcps/marketplace.yaml:4626-4627. The new ~400-character description here sits on one line, so running the generator changes the file (generate-marketplace.yml:56-72 then pushes chore: regenerate marketplace.yaml). This is the only MCP description in the catalog over 240 characters.
Impact: the PR branch receives an extra bot commit, and the committed catalog does not match generator output until it does; no functional impact on install.
Minimal fix: run cd bin && pnpm exec tsx generate-mcps-marketplace.ts and commit the result. The source text in mcps/dc-hub/MCP.yaml:3 is already correct.
Adds DC Hub (
mcps/dc-hub/MCP.yaml) and regeneratesmcps/marketplace.yamlwithbin/generate-mcps-marketplace.ts.What it is: DC Hub is the orchestration layer for data center and energy intelligence. Find power. Find land. Find fiber. Find capacity. One read-only server covers facilities, colocation, power and grid conditions, interconnection queues, energy prices, fiber and site selection, including the Data Center Power Index (DCPI). Its
execute_plantool chains the right tools into one dated, cited answer.Who uses it: people scoping data-center sites and power (developers, site selectors, analysts) who ask their agent where capacity and grid power are available.
https://dchub.cloud/mcpX-API-Keyheader is supported (second install option)cloud.dchub/mcp-serverCategory:
data(external data source).Updated Nov 20, 2026: the description now follows the review bot's suggestion (descriptive rather than an instruction to the agent, no internal key name, no tool count). The YAML parses (
MCP.yamlandmarketplace.yaml).