// SCAN REPORT

Enphase Solar MCP Server

33 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

3 can modify or destroy data

30 read-only

33 tools total

Community server · catalogue entry verified 03/07/2026

How to control Enphase Solar MCP Server ↓

TOOL MAP

What Enphase Solar MCP Server exposes to your agents

Read (30) Write / Execute (3) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Enphase Solar MCP Server tools

Execute · High start_ev_charging Although the description is empty, the tool name and server context make clear this initiates EV charging—an operation that consumes electricity, incurs costs, and has measurable real-world effects. Execute · High stop_ev_charging This tool executes a command that controls physical hardware (EV charger) with immediate real-world consequences. Write · High update_battery_settings This tool modifies battery settings, which are data that control real physical solar battery behavior (charge/discharge rates, reserve levels, etc.).

3 of Enphase Solar MCP Server's 33 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Enphase Solar MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Enphase Solar MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "update_battery_settings": {
    "limits": [
      {
        "counter": "update_battery_settings_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_alarms": {
    "limits": [
      {
        "counter": "get_alarms_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Enphase Solar MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ENPHASE SOLAR →

Instant setup, no code required.

FULL CATALOGUE

All 33 Enphase Solar MCP Server tools

EXECUTE 2 tools

Execute start_ev_charging start_ev_charging Execute stop_ev_charging ⚠️ STOPS PHYSICAL EV CHARGING ⚠️

WRITE 1 tools

Write update_battery_settings update_battery_settings

READ 30 tools

Read get_alarms System alarms within a date range. Read get_battery_settings Read current battery settings (mode, reserve %, schedules). Read get_battery_telemetry Battery telemetry: state of charge (%), charging power, discharging power. Read get_consumption_telemetry Granular consumption telemetry from the consumption meter. Read get_devices All devices in the system: microinverters, batteries, meters. Read get_ev_charger_devices List Enphase IQ EV chargers on the system. Returns serial numbers Read get_ev_charger_events Recent EV charger events for the system. Read get_ev_charger_lifetime Daily lifetime energy data for an Enphase IQ EV charger. Read get_ev_charger_schedules Configured charging schedules for an Enphase IQ EV charger. Read get_ev_charger_sessions Charging session history for an Enphase IQ EV charger. Read get_ev_charger_telemetry Interval energy telemetry for an Enphase IQ EV charger. Read get_event_types Reference: list of event_type_id values with their descriptions and Read get_events System event log (faults, state changes, etc.) within a date range. Read get_grid_export_telemetry Grid-export telemetry at regular intervals. Read get_grid_import_telemetry Grid-import telemetry at regular intervals. Read get_grid_status Current grid status (connected / off-grid) for the system. Read get_latest_telemetry Last reported PV power, consumption power, and battery power in Watts. Read get_lifetime_battery Daily battery charge/discharge totals (Wh). Requires an Enphase battery. Read get_lifetime_consumption Daily consumption totals (Wh) across a date range. Read get_lifetime_grid_export Daily kWh exported to the grid across a date range. Read get_lifetime_grid_import Daily kWh imported from the grid across a date range. Read get_lifetime_production Daily production totals (Wh) across a date range. Read get_live_data Site-level live status. Real-time-ish dashboard data. Read get_load_control_settings Read current load-control settings. Read get_open_alarms All currently-active alarms for the system. Read get_open_events All currently-open events for the system (unresolved issues). Read get_production_telemetry Granular production telemetry from the production meter. Read get_storm_guard_settings Read current Storm Guard settings. Read get_system_summary Current snapshot: latest production power (W), today's energy so far (Wh), Read get_systems List all Enphase systems associated with the developer account.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Enphase Solar MCP Server

How do I prevent bulk modifications through Enphase Solar MCP Server? +

The Enphase Solar MCP Server server has 1 write tools including update_battery_settings. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Enphase Solar MCP Server.

How many tools does the Enphase Solar MCP Server MCP server expose? +

33 tools across 3 categories: Execute, Read, Write. 30 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Enphase Solar MCP Server? +

Register the Enphase Solar MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Enphase Solar MCP Server tool call.

Deterministic rules across all 33 Enphase Solar MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ENPHASE SOLAR →

Instant setup, no code required.

33 Enphase Solar MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.