← All MCP serversModel Context Protocol
Live · Great Plains and SPP West
SPP logo

SPP MCP server

Southwest Power Pool · SPP Integrated Marketplace and public operational data

The SPP MCP server gives compatible AI clients an ISO-bound path into Ask the Grid's Southwest Power Pool catalog. SPP East, SWPW/SPP West, balancing-area, reserve-zone, and market identities remain exactly as the source publishes them; the server does not infer ownership, settlement exposure, or coordinates.

SPP resource URL
https://mcp.askthegrid.com/v1/spp

29

datasets

14

tools

SPP

scope

Streamable HTTP · protocol 2025-11-25

Connect it in about a minute.

Pick your client. Ask the Grid recognizes your signed-in account and shows any authorization already active for SPP.

Checking your Ask the Grid session…

Connect with Claude

Add Ask the Grid as a custom connector, then authorize it with your existing account.

Claude Pro, Max, Team, and Enterprise

  1. 01Open Claude Settings → Connectors.
  2. 02Choose Add custom connector, name it “Ask the Grid SPP,” and paste the resource URL below.
  3. 03Select Add, then Connect. Review the requested scopes and choose Allow.
  4. 04In a conversation, open Search and tools and enable the Ask the Grid SPP tools.
SPP resource URL
https://mcp.askthegrid.com/v1/spp
Official Claude MCP documentation

Once connected

Ask it SPP questions.

01

Compare SPP real-time load and fuel mix with the latest wind and solar forecasts.

02

Which SPP real-time constraints have the largest canonical shadow prices today?

03

Find SPP plants whose published operator or owner fields mention Basin Electric, keeping operated and jointly owned identities separate.

04

Find Basin-relevant SPP substations and lines from public grid records, listing any missing location fields explicitly.

Compare SPP real-time and day-ahead location prices

Track load, fuel mix, renewable forecasts, and operating reserves

Inspect binding constraints and ancillary-service prices

Resolve SPP grid assets: plants, nodes, zones, substations, and lines

Research Basin-relevant public records without inferring ownership or market exposure

Under the hood.

Every credential is audience-bound to SPP. The boundary is enforced in the resource URL, the OAuth audience, the discovery response, and the SQL validator — not by asking the model nicely.

Full tool contracts
search_data

Find query-ready datasets in the connected ISO catalog.

describe_data

Inspect one dataset's schema and semantic query contract.

query_data

Run bounded read-only SQL against ISO-approved tables.

query_grid_assets

Search typed plants, nodes, zones, substations, and lines.

get_live_grid_status

Return current ISO headline values and freshness metadata.

get_asset_profile

Read a compact published profile for one exact grid asset.

get_asset_intelligence

Read an Enterprise source-backed asset intelligence dossier.

Ent
request_asset_hydration

Queue Enterprise hydration for an existing grid asset.

Ent
get_asset_hydration_status

Read the status of one owned asset hydration request.

Ent
get_alert_capabilities

Read the exact market, target, signal, and condition combinations the alert evaluator can execute.

list_alerts

List active alert rules owned by the authenticated user.

get_alert

Read one owned alert rule and its recent activity.

create_alert

Create an alert only from an explicit user request after checking that its threshold and cadence are sensible.

manage_alert

Pause, resume, update, or archive one owned alert after an explicit user request.

Authentication
OAuth 2.1 with PKCE S256
Market boundary
SPP-only audience, allowlist, row caps, audited
Default scopes
mcp:catalog.read · mcp:grid.read · mcp:sql.read · mcp:assets.read
Hydration scope
mcp:assets.write — Enterprise approval required

Questions.

What can the SPP MCP server access?
Only datasets registered for SPP. The resource URL, OAuth audience, discovery responses, and SQL validator all retain the SPP boundary.
Does the SPP MCP server require an account?
Yes. Compatible clients use OAuth 2.1 with PKCE, and you approve the connection while signed in to Ask the Grid.
Can the SPP MCP server change data?
Market and catalog tools cannot change source market data: they are read-only, rate-limited, table-allowlisted, row-bounded, and audited. Separate write scopes can manage only the signed-in user's Ask the Grid alerts or queue an idempotent, reviewed Enterprise asset-hydration request.
Is this SPP MCP server operated by Southwest Power Pool?
No. Ask the Grid operates this MCP server independently. Each catalog record identifies its originating publisher and links to the source publication, including data from SPP Integrated Marketplace and public operational data.
How is MCP different from using SPP Integrated Marketplace and public operational data directly?
The source portal remains the publication of record. The MCP server gives compatible AI clients typed dataset discovery, schema descriptions, ISO-scoped authorization, and bounded read-only queries over Ask the Grid's registered catalog.
What is not available through the SPP MCP server?
The scoped catalog does not currently expose an SPP interconnection queue or operational-event feed. Interchange and DC-tie readings used by live product surfaces do not yet have MCP query contracts, and some public location records have no verified coordinates. Tools return those absences explicitly instead of inventing coordinates, ownership, settlement exposure, or a relationship between SPP East and SWPW/SPP West identities.

Wire SPP into your agent.

Free to connect with an Ask the Grid account.