Iso Ne MCP server

@pipeworx/iso-ne

ISO New England market data via ISO Express web services — five-minute LMPs, system load and generation fuel mix for the six New England states (CT, MA, ME, NH, RI, VT).

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

Tools

congestion and loss components. Omit date for the current interval.

• isonelmp(locationid?, date?, limit?) — five-minute real-time LMP with energy,

hydro, wind, solar, refuse, wood, coal, oil, landfill gas, imports) with the marginal-fuel flag.

• isone_load(date?, limit?) — five-minute total system load in MW.
• isonefuelmix(date?, limit?) — generation by fuel category (gas, nuclear,

Auth

BYO only today. HTTP Basic against webservices.iso-ne.com. Platform fallback env var — not provisioned: PLATFORMISONEKEY.

Registration is free at (an "ISO Express / Web Services" account), but ISO-NE approves the account before the credentials work. A brand-new registration is refused exactly like a wrong password, so the pack's 401 message names the approval step rather than implying the password is wrong.

_apiKey accepts either spelling:

• "username:password" — plain; the pack base64-encodes it.
• base64("username:password") — pre-encoded, same convention as seo-serp.

Anything else fails locally with a clear message instead of becoming a bare upstream 401 that looks like an outage.

One env var, not PLATFORMISONEUSER + PLATFORMISONEPASS: the gateway injects exactly one secret per pack, into apiKey. So the stored credential is the single string the Basic scheme actually needs. The pack is marked byoExpected: true in workers/gateway/src/pack-manifest.json so the vendor-key ratchet does not fail the deploy; drop it the day the credential lands.**

Data sources

/fiveminutelmp/current, /fiveminutesystemload/current, /genfuelmix/current, and /…/day/YYYYMMDD for a historical day.

• — the authenticated API.

• — the public browser UI over the same data.

Traps

2026-09-17, all refused:

• There is no keyless fallback. This was checked, not assumed. Probed

with a browser User-Agent and an isoexpress Referer. Note it is a 403 and not a 404, so the path exists — it is session-gated, not merely UA-gated (cf. referencegovsiteuablocks, where a UA swap is usually the fix).

• webservices.iso-ne.com/api/v1.1/fiveminutesystemload/current → 401
• www.iso-ne.com/ws/wsclient → 500 (for every parameter shape tried)
• www.iso-ne.com/transform/csv/genfuelmix?start=… → 403, and it stays 403

body in this pack has been observed live. ISO-NE wraps results in a singular/plural pair — {"FiveMinLmps": {"FiveMinLmp": [...]}} — and the pack unwraps that generically (descend to the first array-valued property) and returns rows as published, without remapping field names. The envelope field in every response reports which keys it actually walked, so the first real call with a credential tells you the true shape rather than hiding it. Tighten once credentials exist.

• Response shapes here are UNVERIFIED. Holding no account, no ISO-NE response

reports after the fact. The pack treats a 0-row success as an error and says to try the previous day, rather than returning an empty array as a clean answer.

• Same-day requests can legitimately be empty. ISO-NE publishes each day's

appends .json to every path, which is the form the v1.1 API accepts.

• ISO-NE does not use a .json suffix consistently across its docs; this pack

Quick Start

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

{
  "mcpServers": {
    "iso-ne": {
      "url": "https://gateway.pipeworx.io/iso-ne/mcp"
    }
  }
}

Shortened. The full README is on GitHub.