Electricity Maps

Official registry Maps, travel and weather

Electricity Maps MCP — real-time electricity-grid carbon intensity + power generation mix for 200+…

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http electricity-maps 'https://gateway.pipeworx.io/electricity-maps/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "electricity-maps": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/electricity-maps/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-electricity-maps
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

mcp-electricity-maps

Electricity Maps MCP — real-time electricity-grid carbon intensity + power generation mix for 200+ zones worldwide (electricitymaps.com).

Part of Pipeworx — an MCP gateway connecting AI agents to 1855+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
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" })

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "electricity-maps": {
      "url": "https://gateway.pipeworx.io/electricity-maps/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/electricity-maps/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1855+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/electricitymaps_carbon_intensity. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "electricity-maps": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-electricity-maps"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-electricity-maps

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Electricity Maps data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Frequently asked questions

What is Electricity Maps?

Electricity Maps MCP — real-time electricity-grid carbon intensity + power generation mix for 200+…

How do I install Electricity Maps?

It runs as a remote server. In Claude Code: claude mcp add --transport http electricity-maps 'https://gateway.pipeworx.io/electricity-maps/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Electricity Maps need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Electricity Maps open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Electricity Maps?

It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.