Skip to content
Load Factor Docs
Open Load Factor

MCP Tool

Search queue projects

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

  • MCP
  • Read-only
  • Updated

Declaration

MCP tool
search_projects(
    query?: string,
    iso?: string,
    state?: string,
    county?: string,
    fuel?: string,
    developer?: string,
    confidence?: string,
    status?: string,
    min_mw?: number,
    max_mw?: number,
    queue_date_from?: string,
    queue_date_to?: string,
    sort?: string,
    include_duplicates?: boolean,
    limit?: integer,
    offset?: integer
)

Parameters

querystringOptional
Free text: project number/name, developer, SPV, POI substation or county.
isostringOptional
ISO/region, or comma-separated list: PJM, MISO, ERCOT, SPP, CAISO, NYISO, ISO-NE, West, Southeast, IESO, AESO, Maritimes, Quebec, BC, Saskatchewan, Manitoba.
statestringOptional
Two-letter state/province code(s), comma-separated, e.g. 'TX' or 'IL,IN'.
countystringOptional
County name (substring match; a trailing 'County' is ignored).
fuelstringOptional
Fuel(s), comma-separated: Solar, Wind, Offshore Wind, Battery Storage, Hybrid, Hydro, Biomass, Biogas, Biofuel, Wood, Geothermal.
developerstringOptional
Developer / SPV / owner name (substring). Use find_companies first to see name variants.
confidencestringOptional
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).Allowed: confirmed, developer_of_record, any_developer, unknown, allDefault: all
statusstringOptional
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.Allowed: in_queue, live, withdrawn, operating, allDefault: live
min_mwnumberOptional
Minimum summer MW.
max_mwnumberOptional
Maximum summer MW.
queue_date_fromstringOptional
Queue date on/after (YYYY-MM-DD, or YYYY / YYYY-MM).
queue_date_tostringOptional
Queue date on/before (YYYY-MM-DD, or YYYY / YYYY-MM).
sortstringOptional
relevance = developers where two sources agree first, then MW (default); mw; queue_date (newest first); in_service (soonest first).Allowed: relevance, mw, queue_date, in_serviceDefault: relevance
include_duplicatesbooleanOptional
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.Default: false
limitintegerOptional
Rows to return (max 100; your plan may cap lower).Default: 25
offsetintegerOptional
Skip this many rows (paging).Default: 0

Return Value

Returns {summary, total, total_mw, offset, next_offset, filters, results, caveats}, plus operating_projects / operating_mw for status live or all.

Discussion

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.

Example

Ask your assistant:

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

tools/call request
{
  "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.