Solar Data MCP server

☀️ solar-data-mcp

US solar data, agent-accessible.

One MCP server that brings US open solar data to Claude, ChatGPT, and anything else that speaks MCP.

Install one server — uvx solar-data-mcp — and your agent gets all 18 tools, 11 skills that teach it how to use them, and 4 ready-made report prompts, across four data domains: production modeling, economics, market data, and forecasts. Every tool returns the same envelope — data + units + source + assumptions + warnings — so the agent always knows what a number means, where it came from, and which defaults were injected on its behalf.

What can you ask it?

"Is this $21,000 quote fair?" · "What will my array generate tomorrow?"

• Thinking about solar at home — "Would a 6 kW system pay off at my house?" ·

"How long does permitting take in Phoenix?" · "Where should we expand next?"

• Selling or installing solar — "Build a proposal for this customer" ·

installed prices trended in Colorado?" · "Which big plants have batteries?"*

• Studying the market — "Brief me on the Texas solar market" · *"How have

Behind each question the agent picks the right tools (or a skill routes it), and every number comes back with units, a source, and the assumptions made on your behalf.

Quickstart

(or use DEMO_KEY to try it out — 10 requests/hour).

1. Get a free NREL API key —

Claude Desktop, merge this into claudedesktopconfig.json (full example in examples/):

1. Add the server to your agent — snippets for every major agent below; for

{
     "mcpServers": {
       "solar-data": {
         "command": "uvx",
         "args": ["solar-data-mcp"],
         "env": {
           "NREL_API_KEY": "YOUR_KEY_HERE",
           "OPENEI_API_KEY": "YOUR_KEY_HERE",
           "EIA_API_KEY": "YOUR_KEY_HERE"
         }
       }
     }
   }

Only NRELAPIKEY is needed to start: the server runs with any subset of keys, and a tool missing its key returns setup instructions instead of failing silently.

"Compare annual production for an 8 kW system in Mesa, AZ at 10° vs 25° tilt."

1. Restart your client and ask — try

Verify keys and connectivity anytime:

$ uvx solar-data-mcp doctor

Add it to your agent

Claude Code

$ claude mcp add solar-data \
    --env NREL_API_KEY=YOUR_KEY --env OPENEI_API_KEY=YOUR_KEY --env EIA_API_KEY=YOUR_KEY \
    -- uvx solar-data-mcp

(or commit the quickstart JSON to your project's .mcp.json)

Codex CLI — ~/.codex/config.toml:

[mcp_servers.solar-data]
command = "uvx"
args = ["solar-data-mcp"]

[mcp_servers.solar-data.env]
NREL_API_KEY = "YOUR_KEY_HERE"
OPENEI_API_KEY = "YOUR_KEY_HERE"
EIA_API_KEY = "YOUR_KEY_HERE"

(or codex mcp add solar-data --env NRELAPIKEY=YOURKEY -- uvx solar-data-mcp; use envvars = ["NRELAPIKEY"] to forward keys from your shell instead of hardcoding them)

OpenCode — opencode.json in your project (or ~/.config/opencode/opencode.json):

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "solar-data": {
      "type": "local",
      "command": ["uvx", "solar-data-mcp"],
      "enabled": true,
      "environment": {
        "NREL_API_KEY": "YOUR_KEY_HERE",
        "OPENEI_API_KEY": "YOUR_KEY_HERE",
        "EIA_API_KEY": "YOUR_KEY_HERE"
      }
    }
  }
}

Shortened. The full README is on GitHub.