mcpbeat

Eia Energy MCP Server

io.github.cyanheads/eia-energy-mcp-server
answering

Eia Energy MCP Server is answering right now. Last checked 12 min ago. 734 installs a week from npm. It exposes 6 tools. Last commit 1 Aug 2026.

Browse and query the EIA API v2 — electricity, petroleum, natural gas, coal, forecasts via MCP.

Installs per day peak 448 · avg 31 · +1235% w/w
a month agotoday
Uptime history 41 hours of history · worst hour 75%
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
371 ms
Response time
average over 24h
734
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add eia-energy-mcp-server --transport http https://eia-energy.caseyjhand.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "eia-energy-mcp-server": {
      "url": "https://eia-energy.caseyjhand.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.eia-energy-mcp-server]
url = "https://eia-energy.caseyjhand.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "eia-energy-mcp-server": {
      "url": "https://eia-energy.caseyjhand.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "eia-energy-mcp-server": {
      "url": "https://eia-energy.caseyjhand.com/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

eia
eia_browse_routes
Lists child routes under a given path in the EIA dataset taxonomy. Start with no path to get the 14 top-level categories (electricity, petroleum, natural-gas, steo, aeo, ieo, seds, etc.), then drill into subcategories. Each result includes an isLeaf flag — leaf routes are queryable endpoints; non-leaf routes have children to browse. When isLeaf is true on the browsed path itself, switch to eia_describe_route.
eia_dataframe_describe
List canvas dataframes (df_<id>) materialized by eia_query_route, with provenance, expiry, row count, and column schema. Drops entries for dataframes the canvas no longer holds before responding, so the list is always current. Pass a specific name to inspect one dataframe; omit to list all active dataframes for this tenant. A name that is not staged comes back as found=false alongside the handles that are, never as an empty list. Listing is not use: only an eia_dataframe_query statement naming a dataframe extends its expiry, so a dataframe polled with this tool and never queried still lapses on schedule.
eia_dataframe_query
Run a single-statement SELECT against canvas dataframes registered by eia_query_route. Standard DuckDB SQL — joins, aggregates, window functions, CTEs all supported. Reference dataframes by the df_<id> handles returned by eia_query_route or listed by eia_dataframe_describe. Read-only: writes, DDL, DROP, COPY, PRAGMA, ATTACH, and external-file table functions are rejected. System catalogs (information_schema, pg_catalog, sqlite_master, duckdb_*) are denied. EIA data values are VARCHAR — use CAST(col AS DOUBLE) for arithmetic and aggregation. Optional register_as chains results as a new dataframe with a fresh expiry. Every dataframe named in the statement has its expiry extended by the query.
eia_describe_route
Returns metadata for a leaf route: available facets with their valid values, data column names and units, frequency options, and date range. Call this before eia_query_route to discover valid facet IDs, facet values, column IDs, and frequency codes. Each facet returns a capped window of its values with value_count and values_truncated alongside; pass facet and values_offset to page through the rest of one facet. Facet values are fetched from separate EIA endpoints and merged — results are cached per-route for the process lifetime to minimize API calls.
eia_query_route
Fetches data from a leaf route with optional facet filters, date range, frequency, and column selection. Use eia_describe_route first to discover valid facet IDs, facet values, column IDs, and frequency codes. Data values are strings in the response (EIA API returns all numeric values as strings, e.g. "9.13"); cast to DOUBLE in SQL when arithmetic is needed. Returns a preview inline; when canvas is enabled and more rows match than the preview holds, additional pages are fetched and the accumulated set is staged as a DataCanvas table — pass the returned dataset name to eia_dataframe_query for SQL. Every dataset a tenant stages lands in the same canvas, so tables from different routes cross-join by name with nothing to thread between calls.
eia_search_routes
Fuzzy text search across route names, descriptions, and category labels. Resolves natural-language queries like "electricity retail sales by state" or "natural gas imports" to matching route paths. Multi-term queries are also matched term by term, so combining a commodity, a metric, and a sector — "electricity price residential", "coal generation industrial sector" — reaches the route carrying that data even when no single entry reads like the whole phrase. STEO series names are indexed so queries like "ethanol net imports" or "crude oil production forecast" also resolve, and so are facet values, so a fuel type or sector term like "wind" or "anthracite coal" resolves to the route that exposes it, with filter_hint carrying the filter to pass on. Results include isLeaf so you know whether to browse further or query directly. Results with score > 0.72 are weak matches — try a more specific query or use eia_browse_routes to explore the taxonomy. The first call after server start waits 24-30s while the index warms, and at most 45s; every later call returns in milliseconds. Check indexComplete before reading anything into a short or empty result set.

Endpoints

URLTransportStateLatencyChecked
https://eia-energy.caseyjhand.com/mcp streamable-http answering 443 ms 12 min ago

Eia Energy MCP Server — questions

Answers built from our own checks of this server.

What can Eia Energy MCP Server do?
It exposes 6 tools, read directly from the server on our last check. Among them: eia_browse_routes, eia_dataframe_describe, eia_dataframe_query, eia_describe_route, eia_query_route, eia_search_routes. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Eia Energy MCP Server working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 371 ms. The bar chart above shows every period we have measured.
How do I connect Eia Energy MCP Server?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Eia Energy MCP Server need an API key?
No. Eia Energy MCP Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Eia Energy MCP Server?
It answers our handshake in 371 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Eia Energy MCP Server?
The npm package @cyanheads/eia-energy-mcp-server was installed 734 times in the last week. Week over week that is +1235%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Eia Energy MCP Server open source?
Yes — it is published under the NOASSERTION licence, written in TypeScript and 2 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.