Pjm MCP server

@pipeworx/pjm

PJM Interconnection market data via Data Miner 2 — real-time LMPs, generation by fuel type and the seven-day load forecast for the largest US grid operator (13 states + DC, ~65 million people, Illinois to New Jersey).

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

or fetch ANY feed by exact name (dahrllmps, inst_load, …). The escape hatch for the hundreds of PJM feeds without a dedicated tool here.

• pjmfeeds(feed?, rowcount?, start_row?) — list the Data Miner 2 feed catalog,

— five-minute real-time LMP with congestion and loss components.

• pjmlmprealtime(pnodeid?, pnodename?, datetimebeginningept?, row_count?)

by transmission zone and RTO total.

• pjmloadforecast(forecastarea?, rowcount?) — seven-day hourly load forecast

and percentage of total by fuel type.

• pjmgenerationfuelmix(fueltype?, datetimebeginningept?, row_count?) — MW

Auth

BYO only today. Ocp-Apim-Subscription-Key header (Azure API Management). Platform fallback env var — not provisioned: PLATFORMPJMKEY.

A key is free but requires registering an account at and subscribing that account to the Data Miner 2 product. Those are two steps: a registered key that is not subscribed to the feed is refused identically to no key at all, which is why the pack's 401 message names the subscription explicitly rather than just saying "bad key".

Until the key lands, every tool refuses with a message containing requires an API key, and the pack is marked byoExpected: true in workers/gateway/src/pack-manifest.json so the vendor-key ratchet does not fail the deploy. Drop byoExpected the day PLATFORMPJMKEY is provisioned.

Data sources

{ "totalRows": N, "items": [...], "links": [...] }.

• — the browser UI over the same feeds.
• — the API. Documented envelope:

Traps

in this pack has been observed live. The pack normalizes the documented {totalRows, items, links} envelope and returns items as published, without renaming or reshaping individual fields. That is deliberate: a field mapping invented from documentation we could not exercise is a silent-wrong- answer waiting to happen, and returning upstream rows untouched is honest about what we actually know. Tighten this once a key exists and the real payload can be read.

• Response shapes here are UNVERIFIED. Holding no key, no PJM response body

answers 401 with an empty body and no WWW-Authenticate header, both with no key and with a syntactically valid but unregistered one. So 401 cannot distinguish "no key" from "wrong key" from "key not subscribed to this feed". The pack says so in the error rather than guessing at a cause.

• A 401 here tells you almost nothing. Verified 2026-09-17: api.pjm.com

representation. This pack always sets it.

• format=json is not the default — Data Miner 2 defaults to another

filter uses Data Miner's own "M/D/YYYY HH:MM to M/D/YYYY HH:MM" syntax, not ISO-8601.

• Times are Eastern Prevailing Time (EPT — shifts with DST), and the range

always means the date filter fell outside the feed's published range.

• A 200 with 0 rows is treated as an error, not an empty success: it almost

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "pjm": {
      "url": "https://gateway.pipeworx.io/pjm/mcp"
    }
  }
}

What this endpoint actually serves

Shortened. The full README is on GitHub.