
Spp MCP server
online · 100% uptimeReal-time electricity data for SPP, the Southwest Power Pool grid operator covering 14 US states…
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Spp yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Spp tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Spp compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 177 ms
- faster than 68% of 30,031 servers
Release history: 3 versions in the registry since 2026-09-25, latest 2026-10-29, typically one every 32 days.
Install Spp in Claude Code, Cursor or VS Code
claude mcp add --transport http spp https://gateway.pipeworx.io/spp/mcp
What the publisher says
From the Spp repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/spp
SPP (Southwest Power Pool) real-time electricity data — generation mix, load and renewable forecast vs actual, five-minute LMPs, and the raw Marketplace file archive back to 2013, for the 14-state footprint from the Texas panhandle to North Dakota.
Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.
Tools
(coal, gas, nuclear, wind, solar, hydro, diesel fuel oil, energy storage, waste heat, waste disposal, other) plus total load. detailed: true splits each fuel into its Market and Self-scheduled halves over a rolling 365-day feed.
- sppgenerationmix(limit?, detailed?) — MW per fuel per 5-minute interval
and solar forecasts (STLF/MTLF, STWF/MTWF, STSF/MTSF) against actual load, wind and solar.
- spploadforecast(limit?, include_future?) — short- and mid-term load, wind
interval, per settlement location (~1,600), with LMP split into MEC / MCC / MLC.
- spplmplatest(location?, limit?) — the most recently published RTBM 5-minute
Marketplace file archive directly, for a specific historical interval or day.
- spp_files(dataset, path?, download?, limit?) — browse or download the
Auth
Keyless. No registration.
Data sources
vs self-scheduled.
- — current-day generation mix CSV.
- — rolling 365-day, market
forecast vs actual CSV.
- — load/wind/solar
— JSON directory listing of the Marketplace archive.
- &path=&type=folder>
- ?path=> — the file.
Traps
Call portal.spp.org directly so a Worker fetch never depends on redirect handling.
- marketplace.spp.org 302-redirects to portal.spp.org for every API path.
first ~2,000 rows are future intervals with every value blank. A naive rows[0] returns a row of nulls as a clean success. Measured 2026-09-17: 2,017 forecast-only rows in front of 287 settled ones. spploadforecast splits on "does this row have an Actual Load", reports latestactual from the newest settled row, and exposes forecastonly_intervals so the caller can see the split. This is the pack's main reason for existing over a raw CSV fetch.
- The load-forecast CSV is published a week ahead and is newest-first, so the
FILENAMES (RTBM-LMP-SL-202609171905.csv) are Central. Mixing them shifts you five or six hours. Inside the LMP file, Interval is Central and GMTIntervalEnd is UTC.
- Two timezones in one dataset. gen-mix timestamps are GMT; the LMP archive
interval a few minutes late, so the filename for right now is usually a 404. spplmplatest lists the day's By_Interval folder and takes the newest file that exists, falling back to the previous day just after midnight CT.
- Don't compute the "current" LMP filename. SPP publishes each 5-minute
X-SPP-UI-Token header; the server does not require it (verified 2026-09-17), so this pack sends none rather than forge one.
- The file-listing endpoint needs no token. SPP's own UI sends an
- Blank means unknown, not zero. num() returns null for an empty cell.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"spp": {
"url": "https://gateway.pipeworx.io/spp/mcp"
}
}
}What this endpoint actually serves
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Spp: common questions
- Is Spp MCP server safe?
- Mostly: it is graded B (77/100). Read the Spp safety report
- How do I install Spp?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Spp need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Spp maintained?
- The last commit was 40 days ago (2026-09-25). The latest release is v0.2.0.
- Is Spp up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Spp compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 177 ms (faster than 68% of 30,031 servers). Full comparison.