Eia MCP Gridsense logo

Eia MCP Gridsense

Access EIA electricity data for grid fuel mix, demand, state prices, and power-sector CO2 emissions.

Install Eia MCP Gridsense

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "eia-mcp-gridsense": {
      "command": "uvx",
      "args": [
        "eia-mcp-gridsense"
      ],
      "env": {
        "EIA_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The eia-mcp-gridsense MCP server exposes selected US electricity data from the EIA API through four agent-callable tools. It retrieves hourly fuel generation and demand by grid region, plus monthly state price proxies and annual electric-power-sector CO2 emissions. Use it when an agent needs structured electricity-system data and you can provide an EIA API key.

Use cases

  • Compare hourly generation by fuel across grid regions
  • Inspect hourly electricity demand for a region
  • Track monthly state retail price proxies
  • Review annual electric-power-sector CO2 emissions

Key features

  • Hourly fuel-mix data by grid region
  • Hourly electricity demand by grid region
  • Monthly state retail price proxy
  • Annual state power-sector CO2 emissions
  • EIA Open Data API access

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

5/5 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · eia-mcp-gridsense (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit3mo agoMost recent push to the default branch.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Eia MCP Gridsense works

What eia-mcp-gridsense does

The eia-mcp-gridsense MCP server connects an MCP client to the US Energy Information Administration's Open Data API. It makes four electricity-data operations available to an agent:

  • get_fuel_mix returns hourly generation grouped by fuel source for a grid region.
  • get_electricity_demand returns hourly demand for a grid region.
  • get_wholesale_prices returns a monthly retail price proxy for a state.
  • get_co2_emissions returns annual CO2 emissions for a state's electric power sector.

This scope fits questions about regional generation composition, electricity load, state-level price trends, and power-sector emissions. The server is focused on US electricity data exposed through the EIA API rather than general energy data or arbitrary database access.

How it works

An MCP-compatible client starts the server as a local process. The server uses the configured EIA API key to request data from the EIA Open Data API, then exposes the results through the four named tools. The README provides a uvx launch command, so the client configuration runs eia-mcp-gridsense through uvx instead of requiring a separate long-running service.

The available tools divide the data by time resolution and geography. Fuel mix and demand are hourly and use grid regions. Price data is monthly and uses states, while emissions data is annual and covers the electric power sector by state. These distinctions matter when choosing a tool for an agent workflow.

Setup and configuration

Running eia-mcp-gridsense requires an EIA API key. Register for a key through the EIA Open Data registration page, then provide it as the EIA_API_KEY environment variable. The README also allows the value to be stored in a local .env file; that file should not be committed to a repository.

A Claude Desktop configuration can start the server with uvx and pass the key in the server's env block:

config.json
{
  "mcpServers": {
    "eia-mcp-gridsense": {
      "command": "uvx",
      "args": ["eia-mcp-gridsense"],
      "env": {
        "EIA_API_KEY": "your-key-here"
      }
    }
  }
}

Replace the placeholder with the registered key. Keep credentials outside source control.

Tools and capabilities

The eia-mcp-gridsense MCP server provides these capabilities:

  • Query hourly generation by fuel source for a selected grid region.
  • Query hourly electricity demand for a selected grid region.
  • Retrieve monthly retail price proxy data for a selected state.
  • Retrieve annual electric-power-sector CO2 emissions for a selected state.

The README identifies the data source as the EIA API and does not describe additional providers, write operations, authentication methods, or client-specific features beyond the Claude Desktop example.

Limitations and notes

An EIA API key is required, so the server cannot be configured from the documented example without that credential. The available data is limited to the four operations and geographic or time scopes described above. In particular, get_wholesale_prices is described as a monthly retail price proxy, not as a direct wholesale-market price feed. The repository excerpt does not specify response schemas, rate limits, historical coverage, or handling for invalid regions and states.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Eia MCP Gridsense

eia-mcp-gridsense is an MCP server that connects AI clients to the US Energy Information Administration Open Data API. Its main tools retrieve hourly fuel mix, hourly electricity demand, monthly state retail price proxies, and annual electric-power-sector CO2 emissions. It requires an EIA API key.

Run it through `uvx` using the command `eia-mcp-gridsense`. Configure the MCP client with `command: "uvx"`, pass the package name as an argument, and provide `EIA_API_KEY` in the environment.

It requires an EIA API key in the `EIA_API_KEY` environment variable. Obtain the key through the EIA Open Data registration page, or place it in a local `.env` file that is never committed.

The documented client configuration is for Claude Desktop, while the server runs through a standard `uvx` command with `EIA_API_KEY` supplied in the environment.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewEia MCP Gridsense AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/eia-mcp-gridsense?style=directory)](https://allmcps.com/mcp/eia-mcp-gridsense)
HTML Embed
<a href="https://allmcps.com/mcp/eia-mcp-gridsense"><img src="https://allmcps.com/api/badge/eia-mcp-gridsense?style=directory" alt="Eia MCP Gridsense on AllMCPs" /></a>