Skip to content

Cursor DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber get_grid_data

How to: Cursor DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber get_grid_data

client:Cursor transport:streamable-http tool:get_grid_data

Add DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://dchub.cloud/mcp/registry"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    Ask for something get_grid_data does. Cursor lists the server's tools on connect and calls get_grid_data itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber's identifier in your config matches the one above exactly.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.