gridcarbon-mcp
OfficialRelated Servers
Alternatives to gridcarbon-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides real-time grid carbon intensity, power generation breakdown, and carbon-intensity forecasts for any zone or lat/lon location.MIT
- AlicenseNot gradedqualityCmaintenanceEnables users to query current and historical UK electricity carbon intensity, generation mix, and regional intensity data to schedule energy-intensive tasks during low-carbon periods.2 npmMIT
- AlicenseAqualityDmaintenanceProvides real-time electricity grid data including CO2 intensity, power mix, and wholesale prices, plus optimal green time windows for energy-intensive AI tasks. Supports UK, Germany, and global regions with optional API keys.9MIT
- AlicenseAqualityBmaintenanceLive and historical electricity prices, demand, generation mix and carbon intensity for 25 grid zones (US, Europe, GB, Australia). Hosted endpoint plus local stdio bridge; free sample mode, free API key, or x402 pay-per-call.6MIT
- AlicenseBqualityAmaintenanceProvides real-time European and GB electricity grid data via MCP, including generation, prices, carbon intensity, and grid infrastructure.4421 npm6MIT
- AlicenseNot gradedqualityCmaintenanceEnables users to query the UK National Grid's carbon intensity data, providing real-time and forecasted carbon emissions for electricity generation.5 npmMIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: single latest reading, historical series, zone metadata listing, and cross-zone comparison. The descriptions actively cross-reference the other tools with 'Don't use for' guidance, making misselection very unlikely.
All tool names follow a consistent verb_noun pattern in snake_case: get_carbon_intensity, get_intensity_history, list_zones, compare_zones. The verbs (get, list, compare) are descriptive and match each tool's function.
Four tools is well-scoped for a read-only carbon intensity API. Each tool earns its place with no redundancy, and the count falls comfortably within the ideal 3-15 range.
The tool surface covers the full read lifecycle: zone discovery (list_zones), current value (get_carbon_intensity), cross-zone comparison (compare_zones), and historical time series (get_intensity_history). No CRUD operations are needed for this domain, and forecast is not part of the stated data contract, so there are no obvious gaps.