Electricity Maps vs Gridstatus
A side-by-side look at the Electricity Maps and Gridstatus MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Electricity Maps for environment & nature work as a local process; choose Gridstatus for environment & nature as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Electricity Maps when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- You want tools like
electricitymaps_carbon_intensity, electricitymaps_power_breakdown, electricitymaps_carbon_forecast.
Choose Gridstatus when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- You want tools like
gridstatus_datasets, gridstatus_query, gridstatus_latest.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Environment & Nature |
| Quality signal | 59/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | 3 |
| Full listing | View Electricity Maps | View Gridstatus |
Tools & capabilities
Electricity Maps tools 3
electricitymaps_carbon_intensityCarbon intensity (gCO2/kWh) for a grid zone now — the live climate cost of a kWh drawn from the local grid. Pass a zone code (e.g. "US-CAL-CISO", "DE", "FR", "GB") or lat+lon. Example: electricitymaps_carbon_intensity({ zone: "DE", _apiKey: "your-key" })electricitymaps_power_breakdownPower generation mix for a zone — the latest breakdown of electricity by source (nuclear, wind, solar, hydro, coal, gas, ...) plus fossil-free and renewable percentages. Pass a zone code (e.g. "US-CAL-CISO", "DE", "FR", "GB") or lat+lon. Example: electricitymaps_power_breakdown({ zone: "FR", _apiKey: "your-key" })electricitymaps_carbon_forecastCarbon-intensity forecast for a zone — upcoming hourly gCO2/kWh predictions, useful for scheduling loads when the grid is cleanest. Requires a paid Electricity Maps plan. Pass a zone code (e.g. "US-CAL-CISO", "DE", "FR", "GB"). Example: electricitymaps_carbon_forecast({ zone: "GB", _apiKey: "your-key" })
Gridstatus tools 3
gridstatus_datasetsList/search US grid datasets (LMP prices, load, fuel mix across the 7 ISOs: CAISO, ERCOT, PJM, MISO, SPP, NYISO, ISONE). Use this to discover the exact dataset_id to pass to gridstatus_query. Example: gridstatus_datasets({ filter: "caiso lmp", _apiKey: "your-key" })gridstatus_queryQuery a grid dataset's time-series over a time window. Pass a dataset_id from gridstatus_datasets. Common ids: caiso_lmp_real_time_5_min, ercot_load, pjm_fuel_mix. Example: gridstatus_query({ dataset_id: "caiso_lmp_real_time_5_min", start_time: "2026-07-01T00:00Z", end_time: "2026-07-01T06:00Z", li…gridstatus_latestLatest values for a grid dataset — convenience that pulls the most recent rows from a recent window. Pass a dataset_id (e.g. "ercot_load", "caiso_fuel_mix"). Example: gridstatus_latest({ dataset_id: "ercot_load", _apiKey: "your-key" })
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Electricity Maps
{
"mcpServers": {
"electricity-maps": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-electricity-maps"
]
}
}
}
Gridstatus
{
"mcpServers": {
"gridstatus": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-gridstatus"
]
}
}
}
Frequently asked questions
Electricity Maps is categorized under Environment & Nature and uses a local stdio subprocess. Gridstatus belongs to Environment & Nature and uses a local stdio subprocess. Pick Electricity Maps for environment & nature work and Gridstatus for environment & nature.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Electricity Maps has no declared pricing — check the project's own site. Gridstatus has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add electricity-maps and gridstatus as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Electricity Maps has a quality signal of 59/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Gridstatus has 51/100 (Good) with 1 views, 0 installs and 0 GitHub stars.