# Search data-center sites (Load Factor Demand) (`search_data_centers`)

A read-only tool of the Load Factor MCP server (https://mcp.loadfactorenergy.com/mcp), in the Load (data centers) group.

Search Load Factor Demand: data-center sites across North America (operating, under construction, planned and announced) with operator, city/state, ISO (or non-RTO region), status, power capacity today and planned MW, the source of each record, a link to the site in the Load Factor app, and whether Epoch AI's AI data centers dataset covers it. Largest first (the larger of today's and planned MW).

Returns {summary, total, offset, results, next_offset, attribution, caveats}: each result has `id`, `gi_uid` (its Load Factor ID, when assigned), `capacity_mw` / `planned_mw` (omitted when unknown, never 0), `planned_date`, `as_of` (date of the capacity figure or last record update), `source`, `epoch_ai`, `coordinates` (rounded to 0.1 degree, about 10 km, for non-admins, with a `placement` label) and `url`. `next_offset` appears while more rows match; `attribution` carries the OpenStreetMap / Epoch AI licence lines to keep with any answer that uses them.

Filters: iso (PJM, MISO, ERCOT, SPP, CAISO, NYISO, ISO-NE, IESO, AESO, or a non-RTO region such as West or Southeast), state (two-letter codes), operator (substring), status, min_mw (today's or planned MW at least this), query (name, operator, city or campus). Results follow your Load Factor ISO and region permissions. Many sites have no capacity on file; status comes from the source records and can lag. Pass a site's `id` to get_data_center for the generation queued near it and the supply outlook.

## Parameters

| Parameter | Type | Required | Description | Allowed values | Default |
|---|---|---|---|---|---|
| `query` | string | no | Name, operator, city or campus (substring), or a site id. |  |  |
| `iso` | string | no | ISO(s) or non-RTO region(s), comma-separated: PJM, MISO, ERCOT, SPP, CAISO, NYISO, ISO-NE, IESO, AESO, West, Southeast, Quebec, BC, Mexico, ... (NON-ISO = every non-RTO region). |  |  |
| `state` | string | no | Two-letter state/province code(s), comma-separated, e.g. 'VA' or 'TX,OK'. |  |  |
| `operator` | string | no | Operator name (substring), e.g. 'Equinix'. |  |  |
| `status` | string[] | no | Site status(es): operating, under_construction, planned, announced, unknown. | operating, under_construction, planned, announced, unknown |  |
| `min_mw` | number | no | Only sites whose capacity today or planned MW is at least this. |  |  |
| `limit` | integer | no | Rows to return (default 25, max 50). |  |  |
| `offset` | integer | no | Rows to skip, for the next page. |  | 0 |

## Example

Ask your assistant: "List the largest planned and under-construction data centers in PJM."

It would call the tool with a request like this one (your client builds and sends it for you):

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "search_data_centers",
    "arguments": {
      "iso": "PJM",
      "status": [
        "planned",
        "under_construction"
      ],
      "limit": 10
    }
  }
}
```

## Availability

Listed to accounts with the Map module. Results follow your Load Factor permissions (ISOs, detail level, evidence depth and rows per call). See [Access & permissions](https://loadfactorenergy.com/developers/mcp/access-and-permissions).
