aeso-mcp
Related Servers
Alternatives to aeso-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables access to real-time electricity data for a 15-state US region plus Manitoba: fuel mix, five-minute wholesale prices, binding transmission constraints, load and forecasts, and wind/solar output. Can run as a remote MCP endpoint or a local stdio server with no authentication.77 npmMIT
- AlicenseAqualityFmaintenanceOne-call Australian energy-market plumbing via AEMO — cited, structured responses for market data and analysis, not a data broker.5196 PyPIMIT
- AlicenseBqualityDmaintenanceConnects AI agents to energy infrastructure with 30+ tools for managing sites, assets, dispatch, settlements, compliance, and carbon tracking.3450 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query read-only US power market data, including plant generation, emissions, ownership and offtake, plus ISO node and hub prices and basis across seven markets, with sourced results.MIT

kardashev-mcpofficial
AlicenseAqualityCmaintenanceMCP server for Kardashev Labs US grid data, giving agents live LMP, carbon intensity, load, curtailment, interconnection queues, ERCOT large loads, and the public RT-DA spread forecast track record. Requires no API key.1137 npmMIT- AlicenseAqualityBmaintenanceEnables AI agents to perform deterministic, physics-grounded grid connection screening using OpenDSS AC power flow, N-1 and SCR checks, droop compliance, and cryptographic audit receipts. It exposes typed tools and resources for screening, capacity sweeps, and auditable engineering workflows.9MIT
TDQS
Scored across 57 tools
The descriptions are unusually careful about distinguishing related reports, but the 57-tool surface contains dense clusters with overlapping semantics: get_generation/historical_generation/capacity, get_outages/generation_capacity/outage_impact, and supply_adequacy/supply_surplus/assess_supply_tightness/analyze_supply_surplus_eents. An agent could easily select the wrong tool despite the disclaimers, especially among the many analyze_* and summarize_* helpers.
Every tool follows snake_case verb_noun (or verb_adjective_noun) naming: get_, analyze_, calculate_, compare_, summarize_, assess_, explain_, find_, sync_. Acronyms like uc, ffr, and tmr are used consistently within the same pattern. No camelCase or mixed verb styles appear.
57 tools is far beyond the 25+ threshold and will cause selection overhead even if the AESO domain is broad. Many tools could be consolidated behind parameters, such as one outages tool with a type flag, one operating-reserve tool with a report type, or one supply-status tool with an official/derived flag. The set feels like a full REST report catalog rather than a curated MCP surface.
The set covers the core AESO market surface very thoroughly: prices, load, generation, outages, interties, operating reserves, forecasts, settlements, and analytics. Obvious minor gaps exist, such as historical interchange flows and some single-date report lookups, but agents can usually work around these with existing tools.