Eia Mcp Server
Connect your agent to EIA API v2 for electricity, petroleum, gas, coal, and forecast datasets using the leaner @cyanheads/eia-mcp-server npm package.
Overview
EIA MCP is a Build-phase MCP server that queries the EIA API v2 for U.S. energy data via the @cyanheads/eia-mcp-server stdio package.
What is this MCP server?
- Mirrors EIA API v2 domains: electricity, petroleum, natural gas, coal, forecasts
- stdio-only npm package @cyanheads/eia-mcp-server (version 0.1.7 in manifest)
- Same required EIA_API_KEY and DataCanvas TTL defaults as the energy-branded sibling
- EIA_DATAFRAME_DROP_ENABLED flag for optional manual canvas cleanup tools
- Bun runtime hint with start:stdio entrypoint for local MCP clients
- Package version 0.1.7
- npm identifier @cyanheads/eia-mcp-server
- Default EIA_DATASET_TTL_SECONDS 86400
Community signal: 1 GitHub stars.
What problem does it solve?
You have two similarly named EIA MCP packages and need the stdio-only one wired without guessing env vars or API key setup.
Who is it for?
Developers with existing MCP entries pointing at @cyanheads/eia-mcp-server who want local Bun stdio and the same EIA v2 surface.
Skip if: Setups that require the 0.2.x remote at eia-energy.caseyjhand.com without running the local npm package.
What do I get? / Deliverables
Your agent queries official EIA v2 series through the 0.1.7 stdio server once EIA_API_KEY is configured.
- Local stdio MCP tools for EIA v2 dataset browse and query
- Keyed requests to api.eia.gov via configured server process
Recommended MCP Servers
Journey fit
This entry targets the same Build-time need as eia-energy-mcp-server—official U.S. energy stats inside the agent—with a distinct package slug for older or minimal installs. Integrations applies because the server is an MCP transport and tool layer over EIA HTTP APIs, not a standalone analytics product.
How it compares
Sibling stdio package to eia-energy-mcp-server—older 0.1.7 line without the energy remote URL in this manifest snippet.
Common Questions / FAQ
Who is EIA MCP for?
Builders who intentionally install @cyanheads/eia-mcp-server for local agent access to U.S. EIA statistics.
When should I use EIA MCP?
When your MCP config already references eia-mcp-server 0.1.x or you want stdio-only EIA v2 integration during Build.
How do I add EIA MCP to my agent?
Obtain EIA_API_KEY from api.eia.gov, add the npm package with Bun run start:stdio, and register the server in your client’s MCP settings.