# Search operating power plants (`search_plants`)

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

Search EIA power plants (EIA-860/923: built and planned generating plants, not the interconnection queue).

Filters combine with AND. `query` matches plant name or EIA operator/utility (substring), or an exact EIA plant id. Defaults: status operating, renewable fuels only (solar, wind, storage, hydro, geothermal, biomass, biogas); set renewable_only=false to include gas, coal, nuclear or oil plants for emissions or M&A context. `fuel` also takes the queue fuel names search_projects returns ('Battery Storage', 'Offshore Wind', 'Hybrid'): offshore/onshore wind and hybrid (two or more renewable technologies, no fossil unit) are filtered on the EIA-860 technology list. Results include `total`, `total_mw` and a by-fuel breakdown computed over every match, so counts and capacity can be reported without paging. Each row has the EIA operator (eia_operator), capacity factor (0-1), latest CO2, its Load Factor ID (`gi_uid`, when assigned) and a `url` to cite. Plants are a public EIA reference layer and are not limited to your ISOs; queue projects linked to a plant (get_plant) are.

Returns {summary, total, total_mw, by_fuel, offset, next_offset, filters, data_as_of, results, caveats}: `results` is one page of plants, `fuel_legend` names the EIA fuel codes in `primary_fuel`, and `next_offset` is null on the last page. A page can hold fewer than `limit` rows to fit the output size; keep paging from `next_offset`.

Use this for "largest wind farms in Iowa", "NextEra's operating solar plants in Texas", "coal plants in PJM by CO2". For one plant's full dossier (ownership chain, generators, monthly generation, emissions history, PPA prices, grid node, linked queue projects, news) use get_plant. For interconnection-queue projects (proposed, not yet built) use search_projects.

## Parameters

| Parameter | Type | Required | Description | Allowed values | Default |
|---|---|---|---|---|---|
| `query` | string | no | Plant name or EIA operator/utility (substring), or an exact EIA plant id. |  |  |
| `state` | string | no | Two-letter state code(s), comma-separated, e.g. 'TX' or 'IA,MN'. |  |  |
| `county` | string | no | County name (substring match). |  |  |
| `iso` | string | no | ISO market(s), comma-separated: MISO, PJM, CAISO, ISO-NE, ERCOT, NYISO, SPP; or 'none' for plants outside those markets (West, Southeast). |  |  |
| `fuel` | string | no | Fuel(s), comma-separated (any of them matches): solar, wind, offshore wind, onshore wind, hybrid, storage, hydro, geothermal, biomass, biogas, biofuel, wood, gas, coal, nuclear, oil, diesel, waste, other; queue fuel names ('Battery Storage', 'Offshore Wind', 'Hybrid'); or EIA codes (SUN, WND, MWH, WAT, GEO, NG, BIT, SUB, NUC...). |  |  |
| `status` | string | no | EIA plant status. operating (default); planned / under_construction / testing are EIA-860 plants not yet in commercial operation; all = every status. | operating, planned, under_construction, standby, out_of_service, testing, all | operating |
| `renewable_only` | boolean | no | true (default) = renewable primary fuel only; false also returns fossil and nuclear plants. |  | true |
| `owner` | string | no | Owner/operator name substring, matched against the EIA operator/utility. |  |  |
| `min_mw` | number | no | Minimum plant capacity (MW). |  |  |
| `max_mw` | number | no | Maximum plant capacity (MW). |  |  |
| `min_cf` | number | no | Minimum annual capacity factor, as a fraction (0.25) or percent (25). |  |  |
| `sort` | string | no | capacity = largest first (default); co2 = highest latest CO2 first; operating_year = newest first; name = A-Z. | capacity, capacity_factor, co2, operating_year, name | capacity |
| `limit` | integer | no | Rows to return (max 100; your plan may cap lower). |  | 25 |
| `offset` | integer | no | Skip this many rows (paging). |  | 0 |

## Example

Ask your assistant: "What are the largest operating renewable power plants in Texas?"

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_plants",
    "arguments": {
      "state": "TX",
      "limit": 10
    }
  }
}
```

## Availability

Listed to accounts with the Developer Tracker or 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).
