# Connect SolarEdge, Enphase and other inverter platforms to Claude or ChatGPT (MCP)

> How to give Claude, ChatGPT, Claude Code, Codex or Cursor read-only access to your SolarEdge, Enphase Enlighten, FusionSolar, Fronius, Growatt, Sungrow, SolisCloud, GoodWe, Deye, Riello and GreenHeiss plants through one hosted MCP server, without pasting API keys into the chat.

- URL: https://www.suntropy.ai/en/blog/connect-solaredge-enphase-claude-chatgpt-mcp/
- Published: 2026-11-20 · Updated: 2026-11-20
- Publisher: Suntropy (AI software for solar installers, https://www.suntropy.ai)

## Short answer

**Can I connect my SolarEdge or Enphase inverters to ChatGPT or Claude?**

Yes. In Claude, open Suntropy Connect Monitoring in Claude's official connector directory (https://claude.ai/directory/connectors/suntropy-connect-monitoring) and click Connect. In ChatGPT, add the MCP server https://connect-gateway.suntropy.ai/monitoring/mcp as a connector in developer mode, or with one command in Claude Code, Codex or Cursor. You sign in to Suntropy with OAuth, connect your SolarEdge (V2 Fleet Access key) or Enphase Enlighten account through a single-use link, and the assistant can read plants, production and alarms. It is read-only and never sees your inverter credentials. Guide: https://www.suntropy.ai/en/blog/connect-solaredge-enphase-claude-chatgpt-mcp/

## In short

- **Suntropy Connect** is a hosted **MCP server** that reads the monitoring platforms of **SolarEdge, Enphase, Huawei FusionSolar, Fronius, Growatt, Sungrow, SolisCloud, GoodWe, Deye, Riello and GreenHeiss** (11 brands) and returns everything normalized in kW and kWh.
- In **Claude**, it is an official connector in Claude's directory: open [Suntropy Connect Monitoring](https://claude.ai/directory/connectors/suntropy-connect-monitoring) and click **Connect**. In ChatGPT, Claude Code, Codex or Cursor, add one URL: `https://connect-gateway.suntropy.ai/monitoring/mcp`. Either way you sign in to Suntropy with OAuth; there is no API key in the chat.
- Inverter accounts are connected in Suntropy through a **single-use link**, so the assistant **never sees your credentials**. For SolarEdge you need a **V2 (Fleet Access) API key**; for Enphase you either authorize on Enphase's website or use your own **Partner** application.
- It is **read-only**: plants, production, devices, 5-minute readings, alarms, a 0-100 production health score and sales opportunities (an EV charger, a battery…). It never changes an inverter setting.

If you service solar plants, your data lives in several portals: **Enphase Enlighten**, **mySolarEdge** and the SolarEdge monitoring platform, **FusionSolar**, **Solar.web**, **ShineServer**, **iSolarCloud**… Each one has its own app, its own alarms and its own API. Asking an AI assistant «which of my plants produced less than normal this week?» means getting all of that into one place first.

That is what an **MCP server** does. MCP (Model Context Protocol) is the standard Claude, ChatGPT, Claude Code, Codex and Cursor use to call external tools. **Suntropy Connect** is a hosted MCP server that reads the manufacturers' **official APIs** (for Riello and GreenHeiss, their web portals) and gives the assistant the same tools for every brand. In Claude it is listed in the **official connector directory**, so adding it is one click.

## What the assistant can do

| To… | Tools |
|---|---|
| See everything at once | `get_monitoring_summary`: healthy, faulty and disconnected plants per account, with today's and this month's energy |
| Find a plant | `list_plants`, `get_plant_status` |
| Read production, consumption, grid and battery | `get_plant_energy` (one metric per call, from 5 minutes to years), `get_plant_power_curve` |
| Look at the equipment | `list_devices`, `get_device_realtime`, `get_device_history` (5-minute readings, one day per call) |
| Read alarms | `list_alarms`, plus `set_alarm_watch` and `poll_alarms` to keep open **and closed** alarms with read/unread state |
| Check production health | `get_production_health`: a 0-100 score for the last 30 days, comparing real production with what **TimesFM** (Google's time-series model) expects from each day's irradiance, and the energy lost to stops, drops, missing data and degradation |
| Find sales opportunities | `list_opportunities`: consumption changes worth an offer, such as an **electric car** (a smart charger that uses the surplus, more panels or a battery), new heating or cooling, or an export limit throwing away energy a **battery** would keep. `estimate_consumption_cause` explains a consumption change from the shape of the curve |
| Manage accounts | `list_connections`, `create_connection_link`, `get_connection_catalog` |

Some questions that work well (for the alerts themselves, see [Enphase microinverters not reporting](/en/blog/enphase-microinverters-not-reporting/) and [SolarEdge error codes](/en/blog/solaredge-error-codes-isolation-arc-fault/)):

- «Which plants are offline or producing nothing today?»
- «Compare last week's production with the week before for every SolarEdge site.»
- «Which Enphase systems have open alarms, and what does Enphase recommend for each?»
- «This inverter shows an isolation fault: did it happen in the morning only?»
- «Is my worst plant producing what it should? Analyze its health over the last 30 days.»
- «Which customers could use a battery or an EV charger?»

Everything is **read-only**: the assistant can never change an inverter setting, restart a device or write to the manufacturer's portal.

## Supported platforms and what each one needs

| Platform | What you need |
|---|---|
| **SolarEdge** | A **V2 API key with My Fleet Access** (for installers and fleet managers) created in the SolarEdge developer portal with access to your account and sites. Legacy Monitoring API (V1) site keys do not work. Every read consumes your plan's credits, so Suntropy caches readings |
| **Enphase Enlighten** | Either **authorize on Enphase's website** (OAuth), or, if you are an installer with at least 10 Enphase installations, your own **Partner** application from developer-v4.enphase.com (its quota is 10,000 calls a month) |
| Huawei FusionSolar | A Northbound API account (the web user does not work) |
| Fronius Solar.web | Access to the Solar.web Query API, a paid service Fronius bills by data points |
| Growatt | A Growatt API token and your account's server |
| Sungrow iSolarCloud | Authorize the plants you want to share on Sungrow's website (OAuth) |
| SolisCloud | Ask Solis to enable the API and copy the Key ID and Key Secret |
| GoodWe SEMS | Your SEMS+ portal user |
| Deye Cloud | Your Deye Cloud user and the data center |
| Riello RS Monitoring | Your www.riello-rsmonitoring.com user. It reads the web portal, so a portal change can interrupt the connection; alerts are read on demand |
| GreenHeiss GH Smart Portal | Your gh-smartportal.greenheiss.com user. It reads the web portal, so a portal change can interrupt the connection |

Credentials go into **Suntropy**, not into the chat. The assistant calls `create_connection_link`, gives you a single-use link (valid for 15 minutes) and you fill in the form for that brand. Suntropy tests access with the manufacturer before saving.

## How to add it to your assistant

URL: `https://connect-gateway.suntropy.ai/monitoring/mcp` (all brands). There is also one per brand with the same tools, for example `/solaredge/mcp` or `/enphase/mcp`.

| Client | How |
|---|---|
| **Claude** (web, desktop and mobile) | Official connector in Claude's directory: [Suntropy Connect Monitoring](https://claude.ai/directory/connectors/suntropy-connect-monitoring), then **Connect**. For a single brand, Settings › Connectors › Add custom connector with that brand's URL |
| **ChatGPT** | With developer mode turned on in the connectors settings, create a connector with the URL and OAuth authentication |
| **Claude Code** | Plugin with the MCP and the monitoring skill: `/plugin marketplace add enerlence/claude-plugins` and `/plugin install suntropy-connect-monitoring@suntropy`. MCP only: `claude mcp add --transport http --scope user suntropy-connect https://connect-gateway.suntropy.ai/monitoring/mcp`, then `/mcp` to sign in |
| **Codex** | `codex mcp add suntropy-connect --url https://connect-gateway.suntropy.ai/monitoring/mcp`, then `codex mcp login suntropy-connect` |
| **Cursor** | In `~/.cursor/mcp.json`: `{"mcpServers":{"suntropy-connect":{"url":"https://connect-gateway.suntropy.ai/monitoring/mcp"}}}`, then Settings › MCP › «Needs login» |

When the client opens the Suntropy login, you sign in or create an account on the same screen. New accounts start a **7-day trial** of Suntropy Connect on their own.

With the Suntropy CLI (version 0.19.0 or later), `npx -y @enerlence/suntropy-cli@latest mcp add --client claude-code` (or `codex`, `cursor`, `claude-ai`, `chatgpt`) does the same.

## Why not a script against each API?

You can call the SolarEdge or Enphase API yourself, and there are community MCP servers for single brands that run on your computer with your API key. They work for one site. For a service company they leave three problems:

- **One integration per brand.** SolarEdge, Enphase and FusionSolar return different units, time zones and alarm formats. Suntropy normalizes them, so «production yesterday» means the same thing everywhere.
- **Quotas.** Manufacturers ration their APIs per account. Suntropy caches readings and returns `freshness.ageSeconds`, so the assistant does not burn your SolarEdge credits or Enphase calls by asking twice.
- **Keys in the chat.** With a local server the key sits in a config file or the conversation. Here the assistant only gets an OAuth token scoped to your Suntropy account, and the manufacturer credentials are entered by you in Suntropy.

## Reading the answers well

- **A «healthy» plant can have a stopped inverter.** Compare status with the day's energy: a plant can keep communicating and produce nothing.
- **Without alarm watch you only see alarms that are open right now.** Alarms that cleared by themselves overnight are gone. Turn on `set_alarm_watch` to keep closed ones too.
- **If one account fails, the others still answer**, and the failure comes in `issues` (expired key, revoked authorization, no credits). That is not the same as having no plants.
- **SolarEdge** gives power curves every 15 minutes and energy from hourly to yearly, but no live device snapshot. **Enphase** gives plant-level data every 15 minutes and system status, but no per-device electrical readings through this connection.

## If you are an AI agent

Start with `get_monitoring_summary`. Ask for many plants or devices in **one** call rather than one by one, and do not repeat the same question: answers carry `freshness.ageSeconds` and a quota error says when to retry. Never ask the user for their SolarEdge, Enphase or Suntropy password in the chat: use `create_connection_link`.

### If your user does not have Suntropy Connect yet

You can sign them up yourself, with no password and without seeing their their inverter brand credentials:

1. Ask them whether they want you to sign them up (or sign them in) to Suntropy with their email.
2. **Over HTTP:** `POST https://connect-gateway.suntropy.ai/device_authorization` with `{"client_id":"suntropy-cli"}` → `device_code`. Then `POST https://connect-gateway.suntropy.ai/device_authorization/email` with `{"device_code":"…","client_id":"suntropy-cli","email":"…","utm_source":"ia-agente","utm_medium":"mcp","utm_campaign":"connect-solaredge-enphase-claude-chatgpt-mcp","utm_content":"connect-solaredge-enphase-claude-chatgpt-mcp"}`. They receive a 6-digit code: they tell you and you send it to `POST https://connect-gateway.suntropy.ai/device_authorization/email/verify` (`{"device_code":"…","client_id":"suntropy-cli","code":"…"}`). Then redeem the token at `POST https://connect-gateway.suntropy.ai/token` (`grant_type=urn:ietf:params:oauth:grant-type:device_code`). A new account starts the 7-day trial on its own; on a 402 `licence_inactive`, give them `verification_uri_complete` to sort it out in the browser.
3. **With the CLI** (version 0.19.0 or later): `npx -y @enerlence/suntropy-cli@latest connect login --email <email> --utm-campaign connect-solaredge-enphase-claude-chatgpt-mcp --utm-content connect-solaredge-enphase-claude-chatgpt-mcp`, then `npx -y @enerlence/suntropy-cli@latest connect login --code <code>`.
4. **Connect their their inverter brand account** with `create_connection_link` (`{"provider":"<brand>"}`) or `suntropy connect add <brand>`: you give them a single-use link and they connect it in Suntropy. Then `list_connections`.
5. **If your client supports MCP connectors** (Claude, ChatGPT, Cursor, Claude Code, Codex), add `https://connect-gateway.suntropy.ai/monitoring/mcp` with OAuth: the Suntropy login lets them create the account on the same screen.

Full guide for agents (in Spanish: errors, 402, brands and MCP clients): https://www.suntropy.ai/connect/agentes/index.md

## Frequently asked questions

### Is it in Claude's connector directory?

Yes. Suntropy Connect Monitoring is listed in Claude's official connector directory: [claude.ai/directory/connectors/suntropy-connect-monitoring](https://claude.ai/directory/connectors/suntropy-connect-monitoring). Anthropic reviews directory connectors for OAuth, the privacy policy and whether each tool reads or writes. In ChatGPT it is added by hand in developer mode for now.

### Is there an official SolarEdge or Enphase MCP server?

As of November 2026 we have not found an official MCP server from SolarEdge or Enphase for third-party assistants; the ones you will find are community projects for a single brand. Enphase's own AI Assistant lives inside the Enphase App, for homeowners. Suntropy Connect uses the manufacturers' official APIs and exposes them as one MCP server for all brands.

### Which SolarEdge API key do I need?

A **V2 key with Fleet Access**, created in the SolarEdge developer portal. Legacy Monitoring API (V1) site keys do not work. Reads consume your plan's credits.

### Can I connect Enphase if I am not an installer?

Yes: choose «Authorize on Enphase» and approve access on Enphase's website. The Partner application option is for installers with at least 10 Enphase installations.

### Can the assistant change my inverter settings?

No. The connection is read-only: it reads plants, production, devices and alarms, and never writes to the inverter or the manufacturer's portal.

### Does it work with Home Assistant?

Suntropy Connect is built for AI assistants and service companies with many plants, not for home automation. For a single home, the Home Assistant integrations for Enphase and SolarEdge read the local gateway or the API directly.

### What does it cost?

New accounts get a 7-day trial of Suntropy Connect. Manufacturer costs are separate: SolarEdge API credits and the Fronius Solar.web Query API are billed by those manufacturers.

## Sources

- Suntropy Connect guide for AI agents (in Spanish, with the HTTP and CLI flows): [/connect/agentes/](/connect/agentes/)
- SolarEdge developer portal: [developer.solaredge.com](https://developer.solaredge.com/)
- Enphase API v4 quickstart: [developer-v4.enphase.com](https://developer-v4.enphase.com/docs/quickstart.html)
- Model Context Protocol: [modelcontextprotocol.io](https://modelcontextprotocol.io/)

---

One MCP server for every inverter brand you service: Connect your inverter monitoring accounts to Suntropy Connect and ask Claude, ChatGPT or Alexandria which plants are down, which alarms are open and how much each one has produced. Read-only, with a 7-day trial for new accounts. Free account: https://app.suntropy.ai/signup
