For operators reading Sunny Portal and ennexOS
Pexon builds an SMA Monitoring API connector so Claude, ChatGPT or Copilot can read plants, device status and measurements from Sunny Portal and ennexOS on the plant owner's consent. SMA dates more than 900,000 Sunny Portal systems to 04-01-2022. No SMA Monitoring MCP server was named on the developer portal on 6 November 2026.
What we build
Built on what SMA Solar Technology AG documents: plants, plant status, ennexOS devices, plant location, energy and power measurements, device event logs. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.
# sma-monitoring-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
list_plants: # optional name filter -> plants this consent can access, with status when requested
backend: GET /v1/plants
mode: read
get_plant_status: # plant id -> plant status
backend: GET /v1/plants/{plantId}/status
mode: read
list_ennexos_devices: # plant id -> devices on an ennexOS plant, without the plant model and timezone
backend: GET /v1/plants/{plantId}/devices/lean
mode: read
get_plant_measurements: # plant id, set type, period -> power in W or energy in Wh for that set
backend: GET /v1/plants/{plantId}/measurements/sets/{setType}/{period}
mode: read
get_device_logs: # device id -> event logs inside the retention window
backend: GET /v1/devices/{deviceId}/logs
mode: read
get_plant_location: # plant id -> plant location
backend: GET /v1/plants/{plantId}/location
mode: read
audit: every call logged with user, tool, arguments and the SMA Monitoring responseThe manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.
Checked 6 November 2026
| What we found | |
|---|---|
| Interfaces | SMA Monitoring API (REST/JSON, docs public) · SMA GridControl API (REST/JSON, docs public) · SMA Live API (REST/JSON, docs public) · Inverter Modbus (Modbus, docs public) |
| Authentication | The Monitoring API expects an OAuth 2 bearer token in the Authorization header. SMA's access-control page describes an authorization-code grant for an on-screen user and a back-channel flow that emails the plant owner. The owner must hold the system-owner flag on Sunny Portal or the owner role on ennexOS. The same page says that in most cases an installer is not eligible to consent on the owner's behalf. |
| Vendor MCP server | No vendor server. No SMA Monitoring MCP server is named on the developer portal pages read on 6 November 2026. Public GitHub repository searches that day for an ennexOS, Sunny Portal or SMA Solar MCP server returned no repository. |
| Vendor AI assistant | None found. |
| Other connectors | None found. |
SMA Solar Technology AG (DE). Operators and installers of PV systems on Sunny Portal and Sunny Portal powered by ennexOS. SMA's Energy Data Services page, read on 6 November 2026, says more than 900,000 PV systems send data to Sunny Portal and marks that figure Updated: 04-01-2022. That figure is the portal, not a count of Monitoring API clients.
Why SMA Monitoring is hard for agents
01 · Host
Calls go to monitoring.smaapis.de. The connector runs in the customer's network and uses a client the customer registered with SMA. Sunny Portal is not a database on a server in the customer's rack.
02 · Clocks
The FAQ says classic Home Manager, Webconnect and Cluster Controller upload every 15 minutes and processing can take up to 2 hours, or about 15 minutes with a Professional Package in certain countries. ennexOS Data Manager uploads every 5 minutes by default and processes on the fly.
03 · Limits
From 1 July 2025 the catalogue applies a rate limit per credential inside a 5-minute interval. The page does not state the count. SMA also does not allow CORS, so a browser on another origin cannot call the API directly.
04 · Writes
GridControl is the API that changes system settings. The Monitoring file's only POST lists whether commands are supported. Device logs are kept for the last 6 months on ennexOS and the last 3 months on classic systems. Neither the POST nor GridControl is on the manifest.
One interface per row
01
REST/JSON. Documentation is public. OpenAPI read on 6 November 2026, build 1.39. Production host named in the file: monitoring.smaapis.de. 35 GET operations. The one POST stays off the manifest
02
REST/JSON. Documentation is public. the catalogue says this API changes system settings by schedule commands. Its OpenAPI file was not opened, so no path is named, and it is not a tool
03
REST/JSON. Documentation is public. the catalogue says near-time energy balance for WebConnect systems, and not for constant monitoring. Its OpenAPI file was not opened, so no path is named
04
Modbus. Documentation is public. the on-site page names SMA Modbus and SunSpec Modbus. The register lists were not opened, so no register is a tool
SMA Monitoring holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.
When this is the wrong page
If the plants are in meteocontrol VCOM, use that connector. SMA Monitoring reads Sunny Portal and ennexOS. GridControl, which changes system settings, is a different SMA API and is not this page. An SMA Monitoring MCP server was not named on the developer portal on 6 November 2026. If one appears, this page is the read-only restriction, not a second writer.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your SMA Monitoring owners and checks every backend against your release and licence. Week two tests whether a person's own SMA Monitoring permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.
What we need from you: a named SMA Monitoring administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.
Not one that was named on the developer portal pages read on 6 November 2026. Public GitHub repository searches that day for an ennexOS, Sunny Portal or SMA Solar MCP server returned no repository.
Plants the owner has consented to share, plant status, ennexOS devices, plant location, and measurement sets for energy balance, grid settings, sensors and PV energy. Device event logs are kept for the last 6 months on ennexOS and the last 3 months on classic systems. Recent, Day and Week return power in W. Month, Year and Total return energy in Wh.
The plant owner's. SMA's access-control page says an installer is, in most cases, not eligible to consent on the owner's behalf. The owner needs the system-owner flag on Sunny Portal or the owner role on ennexOS. The call then sends that consent as an OAuth bearer token.
The two-week Readiness Blueprint is fixed at €4,900: the tool list, which plants the owner has consented, identity tested end to end, and a costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.
Next step
Thirty minutes with the engineer who would build the connector, with your SMA Monitoring administrator in the room if you like.