Skip to main content

Plant access

The MCP answers for the signed-in SolarSENS identity. It does not treat a Plant name, Plant ID, customer name, or prompt instruction as permission.

What happens on a request​

  1. ChatGPT or Claude sends the request through the authenticated connector.
  2. SolarSENS identifies the connected user.
  3. The service resolves the Plants that user can read.
  4. A tool checks the requested Plant against that scope.
  5. The assistant receives the result, or a clear access or data error.

This is why discovery should come before a detailed read. The discovery result contains the canonical Plant identifier used for the next request.

Customer access and Plant access are different​

Being associated with a customer does not by itself make every Plant visible. The effective Plant list comes from the user's SolarSENS permissions. Two users in the same customer account can therefore receive different results.

What to do when a Plant is unavailable​

  • Check that you signed in with the intended account.
  • Ask the assistant to list your accessible Plants.
  • Use the Plant returned by discovery.
  • Contact AVA Asia if the expected Plant is missing.

Do not paste a shared token into a prompt or ask the assistant to bypass an access result. The MCP is designed to fail closed.

Read-only by design​

The connector can read monitoring information. It does not acknowledge alarms, change configuration, modify work orders, or start an export.

What the connector reads today​

Today the connector reads Plant identity, daily performance, Plant and portfolio dashboards, day charts, device catalogs, device telemetry, string analytics, stored Plant metrics, alarm history, and alarm details. Work-order reads and DataHub exports are not available. Reading an alarm does not acknowledge or clear it.