mcpdirectory.dev
9,129 servers · updated 23 Sept

Solar Home Incentives MCP server

community Active last commit 55 d
{
  "mcpServers": {
    "energyaisolution-solar-home-incentives": {
      "type": "http",
      "url": "https://api.energyaisolution.com/mcp/solar"
    }
  }
}
file .mcp.json (in your project root)version 1.3.0

What it does

MCP server providing US solar production estimates, clean-energy incentives by ZIP code, home energy scoring, and installer routing. For AI agents advising homeowners on solar adoption, energy rebates, and contractor selection.

  • Look up current federal and state solar incentives and rebates available for a specific US ZIP code.
  • Estimate annual solar production in kilowatt-hours for a given system size or monthly electricity bill.
  • Score a home's energy readiness across efficiency, electrification, renewable potential, and financial optimization.

Tools this server exposes

ToolDoes
check_incentivesReturns current US clean-energy incentives (federal, state, utility) for a ZIP code, plus canonical consent text for installer routing.
estimate_productionCalculates honest-range annual solar kWh production for a ZIP code based on system capacity or monthly electricity bill.
get_node_scoreGenerates a 0–100 Energy Node Score across seven dimensions (efficiency, electrification, renewable generation, storage, financial optimization, carbon, market
get_quote_linkGenerates a link for homeowners to request installer quotes without submitting personal details through this tool.
route_leadRoutes a consented homeowner project to vetted local installers; requires prior written consent and timestamp.
list_guidesReturns indexed state-level incentive guides (solar, heat pumps, batteries, weatherization) with source citations.
get_guideRetrieves full text of a state incentive guide including sections, FAQs, and primary sources.
find_local_installersLists publicly-rated clean-energy contractors in a US ZIP or state with reputation scores and review counts.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.