Skip to content

Add DC Hub MCP - #383

Open
azmartone67 wants to merge 7 commits into
Kilo-Org:mainfrom
azmartone67:add-dc-hub
Open

azmartone67 wants to merge 7 commits into
Kilo-Org:mainfrom
azmartone67:add-dc-hub

Conversation

@azmartone67

@azmartone67 azmartone67 commented Oct 13, 2026 •

Copy link
Copy Markdown

Adds DC Hub (mcps/dc-hub/MCP.yaml) and regenerates mcps/marketplace.yaml with bin/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_plan tool 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.

  • Remote, Streamable HTTP: https://dchub.cloud/mcp
  • Works without a key; an optional X-API-Key header is supported (second install option)
  • Repository: https://github.com/azmartone67/dchub-mcp-server
  • Also in the official MCP Registry as cloud.dchub/mcp-server

Category: 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.yaml and marketplace.yaml).

@azmartone67

Copy link
Copy Markdown
Author

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!

@azmartone67

Copy link
Copy Markdown
Author

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!

Comment thread mcps/dc-hub/MCP.yaml Outdated
@@ -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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread mcps/marketplace.yaml Outdated
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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@kilo-code-bot

kilo-code-bot Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: 1 Issue Found | Recommendation: Merge (suggestion only)

Overview

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 1
Issue Details (click to expand)

SUGGESTION

File Line Issue
mcps/marketplace.yaml 1295 Hand-edited generated entry: the ~400-character description stays on one line, which bin/generate-mcps-marketplace.ts (lineWidth: 120) will reflow, so the Generate Marketplace workflow pushes a regeneration commit. Same text in mcps/dc-hub/MCP.yaml:3 (no change needed there).
Files Reviewed (2 files)
  • mcps/dc-hub/MCP.yaml - 0 new issues
  • mcps/marketplace.yaml - 1 suggestion

Verification

Verified at HEAD 830cd6c: the previous CRITICAL is fixed (line 3 is a double-quoted scalar with no embedded quotes or escapes, so : no longer invalidates the YAML), and the previous SUGGESTION is addressed - the description is now capability-focused with no imperative tool directive, no DCHUB_API_KEY key name, and no tool count. Source mcps/dc-hub/MCP.yaml:3 and generated mcps/marketplace.yaml:1295 carry identical text; category: data with the derived tags list, both install variants, the {{DCHUB_API_KEY}} placeholder, and the catalog header (129 MCPs, data: 53) are consistent, and no secret is committed.

Unverified: the new "read-only" claim and the "dated, cited answer" behavior. Commit d4733ca records that the live server added a request_enhancement tool, so confirm the server performs no writes before publishing that wording. The ?via=directory&src=kilo-marketplace install URLs and the upstream repository link also still lack a recorded live-client install test.

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

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 1
Issue Details (click to expand)

SUGGESTION

File Line Issue
mcps/dc-hub/MCP.yaml 3 Description still mixes an imperative agent directive (Call execute_plan first.) with the internal parameter key (DCHUB_API_KEY is optional.). Describe capabilities instead; keep install/parameter detail in content/parameters. Same text at mcps/marketplace.yaml:1295.
Files Reviewed (2 files)
  • mcps/dc-hub/MCP.yaml - 1 suggestion (carried)
  • mcps/marketplace.yaml - 1 suggestion (carried, generated copy)

Verified / Unverified

Verified from the repository: the previous CRITICAL is fixed. mcps/dc-hub/MCP.yaml:3 is now a double-quoted scalar with no embedded quotes or backslashes, so the : in the description no longer makes the file invalid YAML, and the value parses to a single string. mcps/marketplace.yaml (lines 1295, 1306, 1314) matches the source definition field-for-field (id, name, description, author, url, category/tags, content, parameters), and the catalog header unchanged by this diff (129 MCPs, data: 53) still agrees with the added entry. category: data is valid, dc-hub is unique, the API key stays a {{DCHUB_API_KEY}} placeholder, and no secret is committed.

Note: the generated mcps/marketplace.yaml description was hand-edited in commits 4-6 rather than regenerated. Its semantics match the source, but the generator writes with lineWidth: 120 (bin/marketplace-generator-utils.ts:102), so the Generate Marketplace workflow may push a formatting-only follow-up commit; no functional impact.

Unverified: the rewritten endpoint URLs https://dchub.cloud/mcp?via=directory&src=kilo-marketplace are new in this diff and the PR shows no live install test for them. Both install variants (no key, X-API-Key) should be confirmed in a client against the query-string URL, plus the url repository link and the claimed 97-tool count (the PR body still says 94). Maintainers can confirm with cd bin && pnpm exec tsx generate-mcps-marketplace.ts and a real client install.

Fix these issues in Kilo Cloud

Previous review (commit d4733ca)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 1
WARNING 0
SUGGESTION 1
Issue Details (click to expand)

CRITICAL

File Line Issue
mcps/dc-hub/MCP.yaml 3 Description still contains an unquoted : (... energy intelligence: start with execute_plan), which is invalid in a YAML plain scalar. yaml.parse() at bin/generate-mcps-marketplace.ts:34 throws, so generate-mcps-marketplace.ts and the Generate Marketplace workflow cannot process this entry; the same text is regenerated into mcps/marketplace.yaml. Quote the description (as mcps/transform-mcp/MCP.yaml does) or rephrase, then regenerate the catalog.

SUGGESTION

File Line Issue
mcps/marketplace.yaml 1295 Description mixes an imperative agent directive (start with execute_plan) and the internal parameter key (DCHUB_API_KEY is optional) into user/agent-facing catalog text. Describe capabilities instead and keep install/parameter detail in content/parameters; fix at the source in mcps/dc-hub/MCP.yaml and regenerate.
Files Reviewed (2 files)
  • mcps/dc-hub/MCP.yaml - 1 issue (carried)
  • mcps/marketplace.yaml - 1 issue (carried)

Verified / Unverified

Verified from the repository: the incremental commit d4733ca only changes the tool count 96 → 97, and the source and generated catalog remain consistent with each other (no other generated churn). The unquoted-colon parse failure persists on the current head (d4733ca), and the generator's yaml.parse is strict, so the Generate Marketplace workflow will fail until the YAML is fixed. Directory/id/name agree, category data is valid, no duplicate dc-hub id, and the API key uses a {{DCHUB_API_KEY}} placeholder rather than a secret.

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 https://dchub.cloud/mcp, the repository https://github.com/azmartone67/dchub-mcp-server, and the MCP Registry listing cloud.dchub/mcp-server require network access. Maintainers can confirm with cd bin && pnpm exec tsx generate-mcps-marketplace.ts (expected to fail until the YAML issue is fixed) plus a live client install test of both the no-key and X-API-Key variants.

Fix these issues in Kilo Cloud

Previous review (commit 996a29e)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 1
WARNING 0
SUGGESTION 1
Issue Details (click to expand)

CRITICAL

File Line Issue
mcps/dc-hub/MCP.yaml 3 Description contains an unquoted : (... energy intelligence: start with execute_plan), which is invalid in a YAML plain scalar. yaml.parse() will fail, so bin/generate-mcps-marketplace.ts and the Generate Marketplace workflow cannot parse this entry. The same unquoted text is committed in mcps/marketplace.yaml:1295, so the published catalog would also be unparsable. Quote the description (as mcps/transform-mcp/MCP.yaml does) or rephrase, then regenerate the catalog.

SUGGESTION

File Line Issue
mcps/marketplace.yaml 1295 Description mixes an imperative agent directive (start with execute_plan) and the internal parameter key (DCHUB_API_KEY is optional) into user/agent-facing catalog text. Describe capabilities instead and keep install/parameter detail in content/parameters; fix at the source in mcps/dc-hub/MCP.yaml and regenerate.
Files Reviewed (2 files)
  • mcps/dc-hub/MCP.yaml - 1 issue
  • mcps/marketplace.yaml - 1 issue

Verified / Unverified

Verified from the repository: directory/id/name agree (dc-hub), category data is in MARKETPLACE_CATEGORIES, no tags in the source (generator derives it), no duplicate dc-hub id, per-content parameters matches the existing convention (mcps/context7, mcps/atlassian), API key uses a {{DCHUB_API_KEY}} placeholder rather than a secret, and the catalog header/entry counts (129 total, data: 53) are internally consistent.

Unverified: the hosted endpoint https://dchub.cloud/mcp, the claimed tool count (96 here vs 94 in the PR body and earlier comments), the repository https://github.com/azmartone67/dchub-mcp-server, and the MCP Registry listing cloud.dchub/mcp-server require network access. Maintainers can confirm with cd bin && pnpm exec tsx generate-mcps-marketplace.ts (must succeed, which will fail until the YAML issue is fixed) plus a live client install test of both the no-key and X-API-Key variants.

Fix these issues in Kilo Cloud


Reviewed by deepseek-v4.1-flash-1017 · Input: 46K · Output: 14.6K · Cached: 805K

Review guidance: REVIEW.md from base branch main

Comment thread mcps/marketplace.yaml
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."

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant