Skip to main content
Glama
gopisrikrishna

solarnetwork

by gopisrikrishna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to solarnetwork

No user-submitted related servers found.

    Related Servers

    • EnergyAI MCP

      jdhart81
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides free energy intelligence APIs for AI agents: solar production estimates, US clean-energy incentives by ZIP, home Energy Node Scores, contractor search, and consented installer routing.
      MIT

    • Solar Ops MCP

      Ugurluy
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to list demo inverter sites, inspect production, pull weather context, and get deterministic panel-cleaning recommendations over MCP using synthetic solar operations data.
      MIT

    • EnergyAtIt MCP Server

      kasathur
      A
      license
      B
      quality
      D
      maintenance
      Connects AI agents to energy infrastructure with 30+ tools for managing sites, assets, dispatch, settlements, compliance, and carbon tracking.
      34
      23 npm
      1
      MIT
    • Mirador MCP by mirastacklabs-ai

      Mirador MCPofficial

      mirastacklabs-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform observability analysis across Prometheus-compatible metrics and logs without prior vendor knowledge, including signal discovery, entity topology resolution, root-cause analysis, correlation, and capacity forecasting through natural-language anchors.
      Apache 2.0

    • Solar MCP

      ianherzog
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to look up solar permitting authorities, estimate solar production via PVWatts, and retrieve irradiance data. It streamlines the creation of solar-aware workflows by integrating industry-standard APIs like NREL.
      MIT

    • solar-mcp

      hoodsy
      A
      license
      Not graded
      quality
      A
      maintenance
      Open-source MCP servers exposing US solar data (production, resource, economics, market, forecast) as agent-accessible tools with a consistent data envelope.
      MIT
    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.2/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target clearly distinct purposes: discovery, latest reading, aggregated time-series, true energy, quick diagnosis, fleet ranking, ML verdicts, event history, reporting, and node discovery. Two close pairs (query_datum/get_energy and diagnose_site/asset_review) overlap enough that agents could pick the wrong one, but the descriptions explicitly steer usage, keeping misselection risk low.

    Naming Consistency4/5

    Names are uniformly lowercase snake_case and mostly follow a verb_noun pattern (list_sources, get_energy, diagnose_site, create_service_report). Minor deviations: get_latest uses an adjective as the object, and asset_review inverts the verb_noun order, but all names remain easily parseable and predictable.

    Tool Count5/5

    Ten tools is squarely in the well-scoped range for a solar monitoring domain. Each tool earns its place: two for discovery, one for live status, two for historical data access, three for the diagnostics cluster, one for fleet comparison, and one for report generation. No redundant or filler tools.

    Completeness4/5

    The set covers the full analysis lifecycle: discovering public nodes, enumerating sources, reading current state, querying both averaged and true energy, diagnosing faults at both quick and event-level granularity, cross-checking with ML output, comparing sites, and producing serviceready reports. Minor gaps include no raw non-aggregated datum access and no site metadata endpoint, but core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources