{
  "markdown": "# EIA — U.S. Energy Information Administration\n\nThe official US energy data: petroleum, natural gas, electricity, coal, renewables, nuclear, total energy, international energy. Production, consumption, prices, reserves, imports/exports — at national, state, and (for electricity) plant level. Free, requires a free API key.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Why this matters for AI agents\n\nFor energy questions — \"what's the price of natural gas?\", \"how much electricity comes from solar?\", \"are gasoline prices rising?\" — EIA is the source. Government-grade data, no commercial markup. Pair with [FRED](/docs/reference/fred) for energy-related macro indicators and [NOAA](/docs/reference/noaa) for energy-relevant weather context.\n\nCommon flows:\n\n- **Spot prices.** \"What's WTI crude trading at?\" → crude oil spot price series.\n- **State electricity mix.** \"What % of California electricity is solar?\" → state-level generation by source.\n- **Retail gasoline.** \"Average price for a gallon last week?\" → weekly retail prices.\n- **Natural gas storage.** \"How much working gas in storage?\" → weekly EIA-915 reports.\n\n## Auth\n\nEIA Open Data API requires a free key from https://www.eia.gov/opendata/register.php. Pass via `_apiKey`. Generous rate limits.\n\n## Major datasets\n\n| Dataset | Cadence | Use |\n|---|---|---|\n| Petroleum & Other Liquids | Weekly / monthly | Crude oil prices, gasoline, distillates, OPEC |\n| Natural Gas | Weekly storage, monthly production | Pricing, storage, consumption |\n| Electricity | Monthly | Generation by fuel, retail rates by state |\n| Coal | Monthly / annual | Mining, prices, exports |\n| Renewable & Alternative Fuels | Monthly | Solar, wind, biofuels, electric vehicle charging |\n| Total Energy / Annual Energy Outlook | Annual | Long-term forecasts |\n\n## Series IDs\n\nEIA series follow `dataset_id.frequency.region.product` patterns. Examples:\n\n- `PET.RWTC.D` — WTI crude, daily\n- `NG.RNGC1.D` — Natural gas Henry Hub, daily\n- `ELEC.GEN.SUN-CA-99.M` — California solar generation, monthly\n- `PET.EMM_EPMR_PTE_NUS_DPG.W` — US weekly average regular gasoline price\n\nUse the `eia_search` tool to find IDs rather than constructing them manually.\n\n## Common pitfalls\n\n- **Reporting lag varies.** Petroleum prices update weekly with ~3-day lag. Electricity generation is monthly with ~2-month lag. Don't assume \"current\" matches across datasets.\n- **Heat content vs volume.** Natural gas reported in BCF (billion cubic feet), MMcf, and energy units (BTU, MMBtu). Conversions matter for cross-fuel comparison.\n- **Net vs gross generation.** Power-plant generation has subtle definitions. \"Net\" subtracts plant-internal use. EIA mostly publishes net. Don't double-count.\n- **State electricity by primary mover.** EIA's state-level mix is by primary mover (steam turbine, combined cycle, etc.) AND fuel — same plant can have multiple categorizations. Aggregate to the level your question requires.\n- **Forecasts are scenarios.** AEO (Annual Energy Outlook) is a reference-case projection plus side-cases. Don't treat reference case as \"what will happen.\"\n- **No market-real-time prices.** EIA spot prices are official end-of-day; for intra-day market prices you need a commercial feed, not EIA.\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"eia\": {\n      \"url\": \"https://gateway.pipeworx.io/eia/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/eia/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Eia data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 5311,
  "sha": "b7fa9e98cc29b5fe353b3ad6eda3b2ec41b2acdc23f54c480f4c8bafcde5fae2",
  "repo_slug": "pipeworx-io/mcp-eia",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_eia_c2f67947/readme"
}