# Changelog

New features and changes to the Load Factor MCP server and these docs.

Each entry lists what changed and links to the pages that cover it, newest first.

## November 14, 2026

### Site view on operating plants

Release 1.00.342. [Site view](https://loadfactorenergy.com/developers/guide/site-view) is now on operating plant pages too, with the same imagery, time-lapse and inferred signals. A plant's before image shows the land before it was built (for plants operating since 2018), and a plant that has run unchanged gets **No visible change at the plant**. The signals now sit in one strip above the image, and the image uses the full width of the page.

### Videos re-recorded for Load Factor

Release 1.00.339. The how-to videos in these docs and the [user guide](https://loadfactorenergy.com/developers/guide) are re-recorded for Load Factor, on the app as it is today. One is new: signing in, with the launch screen, in [Get around Load Factor](https://loadfactorenergy.com/developers/guide/getting-started#sign-in).

Release 1.00.341 adds a video to [Site view](https://loadfactorenergy.com/developers/guide/site-view): before and after, the signals, the quarterly time-lapse, and what the tab says when a project's location is approximate.

### New home: loadfactorenergy.com

Release 1.00.318. The site is now [loadfactorenergy.com](https://loadfactorenergy.com), and the app, sign-in and API are at [app.loadfactorenergy.com](https://app.loadfactorenergy.com). The data-center and large-load product, formerly Load, is now **Load Factor Demand**.

The MCP server keeps its current address, `mcp.loadfactorenergy.com`, for now, so connectors you already added need no change; we'll announce any change in this changelog. The [Claude Code](https://loadfactorenergy.com/developers/mcp/claude-code) examples now name the server `load-factor`; a server you added under another name keeps working under that name.

## October 29, 2026

### A single bearer token for agent platforms

A service account can now hold a [single bearer token](https://loadfactorenergy.com/developers/mcp/service-accounts#single-bearer-token) for agent platforms that can store only one secret and cannot run the client-credentials grant. The agent sends it as `Authorization: Bearer` straight to the MCP server, with the same read-only tools, rate limits and logging; the token endpoint does not accept it. A client credential remains the safer choice where the platform supports it.

### Service accounts for agents, and Load Factor Demand tools

Agents that run unattended can now connect without a browser sign-in. A Load Factor admin creates a read-only [service account](https://loadfactorenergy.com/developers/mcp/service-accounts) and mints a credential for it; the agent exchanges the client ID and secret for an access token (the OAuth client-credentials grant) and calls the read-only tools. Each credential has its own rate limits, can be rotated or revoked at any time, and every request it makes is recorded.

Two new tools cover Load Factor Demand: [`search_data_centers`](https://loadfactorenergy.com/developers/tools/search_data_centers) lists data-center sites by market, state, operator, status and size, and [`get_data_center`](https://loadfactorenergy.com/developers/tools/get_data_center) returns one site with the generation queued near it, by fuel and status, and the supply outlook the Load Factor app shows. `data_catalog` gains a `load` topic.

### Evidence titles and notes read like the web app

An evidence record's `document_title`, `notes` and quoted text now carry what the source itself says: the filing or article title, docket and accession numbers, dates, contract terms and company names as filed, without the annotations we keep for our own records. A record whose title was only such an annotation is titled with its source label. This applies to the MCP tools, to REST requests made with an API key, and to the project workbook and Orange Button exports. Fields and filters are unchanged.

## October 28, 2026

### Evidence sources now use the same labels as the web app

Every evidence record now names its source the way the Load Factor web app does ("Interconnection agreement", "ISO queue (official)", "SEC subsidiary list (Ex-21)" and so on), with a `source_family` and a `strength` word (Strong, Supporting or Lead) in place of internal source codes and numeric levels. This applies to the MCP tools, to REST requests made with an API key, and to the project workbook and Orange Button exports. [`get_project_evidence`](https://loadfactorenergy.com/developers/tools/get_project_evidence) counts records `by_source` and `by_family` and takes new `source`, `family` and `min_strength` filters; its older `source_type` and `max_tier` filters still work but are deprecated. See [Evidence sources and strength](https://loadfactorenergy.com/developers/tools#evidence-sources-and-strength).

## October 10, 2026

### SEC company intelligence

Load Factor now links companies to their SEC EDGAR filings, after analyst review. Three new tools: [`sec_search_companies`](https://loadfactorenergy.com/developers/tools/sec_search_companies) finds registrants by name, ticker or CIK; [`sec_company_filings`](https://loadfactorenergy.com/developers/tools/sec_company_filings) lists a registrant's filings with sec.gov links; [`sec_company_subsidiaries`](https://loadfactorenergy.com/developers/tools/sec_company_subsidiaries) returns its latest reported subsidiaries and the queue projects linked to them. [`get_company_profile`](https://loadfactorenergy.com/developers/tools/get_company_profile) gains a `sec` section, [`get_project`](https://loadfactorenergy.com/developers/tools/get_project) a `sec_parent` section, [`find_companies`](https://loadfactorenergy.com/developers/tools/find_companies) and `search` results carry the `cik`, and `fetch` accepts `company:cik:<n>`. An SEC parent is the owner as of fiscal year-end, not the developer; see [SEC company intelligence](https://loadfactorenergy.com/developers/mcp/sec-company-intelligence).

## September 26, 2026

### Load Factor Insights in Claude and ChatGPT

Load Factor's published research is now available through the MCP server. [`search_insights`](https://loadfactorenergy.com/developers/tools/search_insights) finds articles by topic, market, date or text; `fetch` with an `article:<slug>` id returns the whole article; and `search` (used by ChatGPT deep research) now includes up to two matching articles alongside queue data. See [example prompts](https://loadfactorenergy.com/developers/mcp/example-prompts#load-factor-research).

### Load Factor MCP server is generally available

Connect Load Factor to Claude (web, desktop, mobile and Claude Code), ChatGPT (developer mode, deep research and company knowledge) and other MCP clients at `https://mcp.loadfactorenergy.com/mcp`.

- 26 read-only tools across queue projects, companies, power plants, PPAs, deals and news, grid and market data, and siting, plus 3 resources and 5 prompt templates. See [MCP tools](https://loadfactorenergy.com/developers/tools).
- Sign in with Google. Access is switched on per account by your Load Factor admin and follows your Load Factor plan.
- Every request is recorded and visible to your Load Factor admins.

### Developer docs

These docs launch with a [quickstart](https://loadfactorenergy.com/developers/mcp/quickstart), setup guides for each client, [example prompts](https://loadfactorenergy.com/developers/mcp/example-prompts) and a reference page for every tool. Every page is also available as Markdown: add `.md` to its address, or use **Copy page**.
