Skip to main content
Glama
holger1411

unofficial-solaredge-mcp

by holger1411
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SOLAREDGE_API_KEYYesYour SolarEdge Monitoring API key
SOLAREDGE_SITE_IDYesYour SolarEdge site ID (integer)
SOLAREDGE_BASE_URLNoAPI base URLhttps://monitoringapi.solaredge.com

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
solaredge_live_statusA

Current power, energy flow (PV/battery/grid/load), battery charge level, and today/this-month/lifetime production for the configured site. energy_today_wh is AC production; pv_generation_today_wh adds the energy stored in the DC-coupled battery and matches the SolarEdge app/HEMS.

solaredge_energy_analysisA

Energy balance and derived metrics (self-consumption rate, self-sufficiency) over a period. time_range: today|1d|1w|1m|3m|1y|custom. For 'custom' supply start_date and end_date as 'YYYY-MM-DD HH:MM:SS'. meters: optional comma list (Production,Consumption,SelfConsumption,FeedIn,Purchased). The summary reports both ac_production (inverter AC meter) and pv_generation (= AC + net battery storage), the latter matching the SolarEdge app/HEMS for DC-coupled batteries.

solaredge_diagnosisB

System health: inverter status/firmware, data freshness, and (for check_type='comprehensive') battery state of charge and State of Health. check_type: health|performance|comprehensive.

solaredge_forecastA

Heuristic production estimate from the historical daily average (no weather data). forecast_type: daily|weekly.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool serves a clearly distinct purpose: diagnosis for system health, energy analysis for historical metrics, forecast for production estimates, and live status for current data. No overlaps or ambiguity.

Naming Consistency5/5

All tools follow a consistent 'solaredge_' prefix followed by a descriptive verb_noun pattern (e.g., live_status, energy_analysis). Naming is uniform and predictable.

Tool Count5/5

Four tools cover the core aspects of solar monitoring: health, historical analysis, forecast, and live status. The count is appropriate for the domain without being excessive or insufficient.

Completeness4/5

The set covers essential monitoring and analysis functions. Minor gaps exist, such as missing tools for site configuration, alerts, or detailed component history, but core workflows are supported.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources