FindEnergyRates MCP Server

Connect Claude — or any MCP client — directly to live US retail electricity data.

Ask "what's the cheapest 12-month fixed plan for Oncor in Dallas?" or "how does 11.4¢ compare to PECO's price to compare?" and get an answer from current market data instead of a guess.

What you get

Three read-only tools:

search_plans

Live residential electricity offers for one utility in one state, cheapest first. Filter by contract length and renewable content. Returns supplier, plan name, rate in cents per kWh, monthly and cancellation fees, and a signup link where we have one.

get_ptc_rates

The utility price to compare — the regulated default-service rate a competitive offer is measured against. This is the number that decides whether a plan is actually a good deal. Current period only.

get_utility_by_zip

Resolves a ZIP code to the utility serving it, including the Texas TDSP. Where a ZIP straddles two service territories it returns both, because which one serves a given address depends on the address, not the ZIP.

What it will not do

It is read-only. It cannot enroll you in a plan, submit anything, or produce a binding quote. The database role behind it has read access to four published views and no ability to write anything at all.

Coverage

We track deregulated markets in these states; price-to-compare is available where a regulated default-service rate exists (Texas has none because it is fully deregulated — a fact about Texas, not a gap in our data).

Plan markets
CT · DC · DE · IL · MA · ME · NJ · NY · OH · PA · RI · TX
Price to compare
DC · DE · IL · MA · ME · NJ · NY · OH · PA · RI

We say "no data," never "no plans." Plan results only include offers we have seen in the last 7 days. When we have not refreshed a market recently, the server says exactly that (no_data_for_scope) rather than returning an empty list — so your assistant can tell you "no current data" and never "there are no plans available," which would be a very different and much worse claim.

Getting a key

Email support@findenergyrates.com and ask. That is the whole process — there is no signup portal yet. Tell us roughly what you are building and we will send a key back. Free-tier keys are rate limited per day, which is plenty for interactive use.

Connecting

Once you have a key, add the server to Claude Code:

claude mcp add --transport http findenergyrates https://findenergyrates.com/mcp \
  --header "Authorization: Bearer YOUR_KEY_HERE"

Or add it to claude_desktop_config.json / any MCP client that speaks remote servers:

{
  "mcpServers": {
    "findenergyrates": {
      "type": "http",
      "url": "https://findenergyrates.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY_HERE" }
    }
  }
}

Start a new session after adding it — MCP servers are loaded at startup.

Cursor, Windsurf and other clients that speak remote HTTP with custom headers work the same way. The claude.ai web "custom connector" dialog does not — it only takes OAuth client credentials, and this server uses a static key. Use Claude Code or Claude Desktop instead.

Send your key in the Authorization header only. Keys in a query string are rejected; we store only a hash of your key and cannot recover one that leaks.

Limits and honesty

Questions

support@findenergyrates.com