Model Context ProtocolCaliforniaCAISO:MCP
CAISO logo

CAISO MCP server

California Independent System Operator

The CAISO MCP server exposes Ask the Grid's California market catalog through ISO-bound discovery and read-only query tools. Every credential is audience-bound to CAISO's MCP resource.

Connect the CAISO MCP server

Choose the AI client you use. Ask the Grid recognizes your signed-in account and shows active authorizations for this market.

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 CAISO,” 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 CAISO tools.
CAISO resource URL
https://mcp.askthegrid.com/v1/caiso
Official Claude MCP documentation

Overview

A market-scoped path from compatible AI clients into Ask the Grid’s CAISO catalog and reviewed asset intelligence.

01

Analyze real-time and day-ahead LMPs

02

Compare CAISO demand, renewables, and net load

03

Inspect congestion components and market intervals

04

Resolve California plants, pricing nodes, zones, and lines

05

Read published asset dossiers or request reviewed Enterprise hydration

Tools

Typed actions for catalog discovery, bounded data reads, live grid context, and reviewed asset intelligence.

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.

Enterprise
request_asset_hydration

Queue Enterprise hydration for an existing grid asset.

Enterprise
get_asset_hydration_status

Read the status of one owned asset hydration request.

Enterprise

Data available

16 catalog-registered datasets are queryable through this CAISO resource. Each dataset retains its source, schema, coverage, and query notes.

Browse the full data catalog

Example prompts

Questions a connected client can answer with the CAISO resource.

  1. 01Show the highest CAISO real-time LMPs this morning.
  2. 02Compare solar generation with net load through today's evening ramp.
  3. 03Find gas plants near a named CAISO pricing node.
  4. 04Get the published intelligence dossier for this plant, or request hydration if it is missing.

Access and authorization

The client discovers Ask the Grid’s authorization server, sends you through sign-in, and asks you to approve the exact scopes it needs.

Authentication
OAuth 2.1 with PKCE S256
Default scopes
mcp:catalog.read · mcp:grid.read · mcp:sql.read · mcp:assets.read
Hydration scope
mcp:assets.write · Enterprise approval required
Safety boundary
CAISO-only audience, table allowlist, row limits, and audited calls

Opening the resource from a compatible client while signed out routes through the standard Ask the Grid sign-in page before the authorization screen.

Frequently asked questions

What can the CAISO MCP server access?
Only datasets registered for CAISO. The resource URL, OAuth audience, discovery responses, and SQL validator all retain the CAISO boundary.
Does the CAISO 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 CAISO MCP server change data?
Market and catalog tools are read-only, rate-limited, table-allowlisted, row-bounded, and audited. Enterprise users can separately approve a write scope that only queues an idempotent, reviewed asset-hydration request.

Switch resources to change the code-owned ISO boundary.