
Eia Mcp Gridsense
io.github.pranavbhosale25Published by GitHub account pranavbhosale25v0.1.0Updated Oct 27, 2026
MCP server for US electricity grid data: fuel mix, demand, retail prices, CO2 emissions
Overview
Local MCP server that gives an assistant US electricity grid data from the EIA API: fuel mix, demand, retail prices and CO2 emissions.
- What you can do
- Retrieve hourly generation by fuel source for a grid region
- Retrieve hourly electricity demand for a grid region
- Look up a monthly retail price proxy for a state
- Look up annual CO2 emissions by state for the electric power sector
- When to use it
- Useful when you want an assistant to answer questions about the US power grid — how electricity is being generated, how much demand there is, what retail prices look like, or state-level power-sector emissions — without leaving the chat.
- Requirements
- Runs locally over stdio, typically launched with uvx from the PyPI package eia-mcp-gridsense, so Python tooling is needed. Requires an EIA API key supplied in the EIA_API_KEY environment variable; keys are obtained by registering with EIA. Network access to the EIA API is required.
Installation
In SourceWeft
- Open Eia Mcp Gridsense in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
eia-mcp-gridsense
An MCP server exposing US electricity grid data from the EIA API:
get_fuel_mix— hourly generation by fuel source for a grid regionget_electricity_demand— hourly demand for a grid regionget_wholesale_prices— monthly retail price proxy for a stateget_co2_emissions— annual CO2 emissions by state, electric power sector
Setup
Requires an EIA API key: https://www.eia.gov/opendata/register.php
Set it as an environment variable (or in a local .env file, never committed):
Usage with Claude Desktop
Source: README.md at commit 0b7f6ad
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.