kj / agent-ready

Public implementation · SolarSENS

SolarSENS: a read-only MCP connection

A practical example of how an AI assistant can work with real operational data without being given permission to change it.

Discuss your project ↗Try the free scan

The problem

Solar plant operators need to find and interpret information across plants, devices, performance records and alarms. A conversational interface can help people ask questions in the tools they already use.

The public implementation

SolarSENS documents a production MCP connection for compatible AI clients, including ChatGPT and Claude. Its public guide describes a read-only server that checks the user’s access and returns monitoring data for permitted plants.

  • Search or list accessible plants and inspect plant overviews.
  • Retrieve available performance, device telemetry, charts and alarm information.
  • Use account-specific access; write, update and delete operations are unavailable.

Why it matters

The example separates discovery from action: an assistant is given clearly defined read-only tools instead of unrestricted access to an operational system. This page describes the publicly documented implementation; it does not claim a measured business outcome.

Explore the public SolarSENS AI guide ↗