# Search queue projects (`search_projects`)

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

Find renewable interconnection-queue projects and who is developing them.

Filters combine with AND. `query` matches project number, project name, developer, interconnection customer (SPV), owner, POI substation and county (case-insensitive substring). Results are ordered by developer confidence (two sources agree first) then MW, and include `total` and `total_mw` over all matches so you can report counts without paging. Each row carries `developer_confidence` (the web app's badge as a code: `confirmed` = two sources agree, `developer_of_record` = named in the queue, `inferred`, `unknown` = not identified), a plain-English `confidence_label` saying why, and a `url` to cite. Default status='live' = not withdrawn, INCLUDING operating plants (the summary says how many are operating); status='in_queue' is the not-yet-built pipeline. PJM duplicate rows are excluded unless include_duplicates=true.

Returns {summary, total, total_mw, offset, next_offset, filters, results, caveats}, plus `operating_projects` / `operating_mw` for status live or all. `results` is one page of project rows (queue fields, developer, SPV, owner, the confidence fields and `url`); continue with `offset` = `next_offset` (null on the last page). Only `confirmed` (two sources agree) rests on two independent strong records. `caveats` flags approximate MW (West, Southeast and CAISO publish MW in buckets) and that PJM MW is capacity (CIR) MW, not nameplate. A capped page carries `truncated` and a `truncation_note`.

Use this for lists ("solar projects in Texas over 200 MW", "NextEra's queue projects in PJM", "storage projects in CAISO where two sources agree on the developer"). For one project's full dossier use get_project; for counts/MW by group use queue_stats.

## Parameters

| Parameter | Type | Required | Description | Allowed values | Default |
|---|---|---|---|---|---|
| `query` | string | no | Free text: project number/name, developer, SPV, POI substation or county. |  |  |
| `iso` | string | no | ISO/region, or comma-separated list: PJM, MISO, ERCOT, SPP, CAISO, NYISO, ISO-NE, West, Southeast, IESO, AESO, Maritimes, Quebec, BC, Saskatchewan, Manitoba. |  |  |
| `state` | string | no | Two-letter state/province code(s), comma-separated, e.g. 'TX' or 'IL,IN'. |  |  |
| `county` | string | no | County name (substring match; a trailing 'County' is ignored). |  |  |
| `fuel` | string | no | Fuel(s), comma-separated: Solar, Wind, Offshore Wind, Battery Storage, Hybrid, Hydro, Biomass, Biogas, Biofuel, Wood, Geothermal. |  |  |
| `developer` | string | no | Developer / SPV / owner name (substring). Use find_companies first to see name variants. |  |  |
| `confidence` | string | no | confirmed = two sources agree: two or more independent strong records name the developer; developer_of_record = named in the queue: the grid operator's queue names it and nothing else strong does yet; any_developer = a developer is named at any confidence; unknown = not identified: no developer identified; all (default). | confirmed, developer_of_record, any_developer, unknown, all | all |
| `status` | string | no | Queue status filter. live (default) = not withdrawn/suspended, INCLUDING projects already operating/in service; in_queue = not withdrawn and not yet operating (the development pipeline); operating = in service; withdrawn = withdrawn/suspended/cancelled; all = everything. | in_queue, live, withdrawn, operating, all | live |
| `min_mw` | number | no | Minimum summer MW. |  |  |
| `max_mw` | number | no | Maximum summer MW. |  |  |
| `queue_date_from` | string | no | Queue date on/after (YYYY-MM-DD, or YYYY / YYYY-MM). |  |  |
| `queue_date_to` | string | no | Queue date on/before (YYYY-MM-DD, or YYYY / YYYY-MM). |  |  |
| `sort` | string | no | relevance = developers where two sources agree first, then MW (default); mw; queue_date (newest first); in_service (soonest first). | relevance, mw, queue_date, in_service | relevance |
| `include_duplicates` | boolean | no | Include PJM duplicate rows (the older '<id>' row whose queue position moved to '<id> - moved to TC1/TC2', and '<id> <number>' copies of '<id>-<number>'). Default false so counts and MW are not double-counted. |  | false |
| `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: "List the 10 largest solar projects in ERCOT's interconnection queue, with their developers."

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_projects",
    "arguments": {
      "iso": "ERCOT",
      "fuel": "Solar",
      "sort": "mw",
      "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).
