# Test connection

Use MCP Inspector to confirm that SolarSENS MCP is reachable and that your account sees the correct read-only tools, independent of any AI app.

## Before you start

* Install [MCP Inspector](https://modelcontextprotocol.io/docs/tools/inspector).

* Get your email allowed. See [Sign in](https://ai.solarsens.co/docs/installation/sign-in.md).

* Use this server URL:

  ```
  https://ops.solarsens.co/mcp
  ```

## Connect over OAuth

1. Open MCP Inspector and enter the server URL above.
2. Choose the streamable HTTP transport.
3. Start the connection. Inspector opens the SolarSENS sign-in page.
4. Sign in and approve the read-only connection.

Inspector needs no client secret.

## List the tools

Open the **Tools** tab. A signed-in session shows these tools and no others:

| Tool                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `get_profile`                 | Return the email address for the SolarSENS account selected for this connection. Use to confirm which account is connected. Does not select or switch accounts. Read-only.                                                                                                                                                                                                                                                                                                                                                                                                                        |
| `list_accessible_plants`      | Read the current Plant catalog for the signed-in account, all accessible Plants. Use only returned Plant IDs; never guess account scope from letters, digits, keywords, or IDs. Use for: account scope. Not for: a named Plant - use search\_plants. Next: get\_portfolio\_dashboard. Read-only.                                                                                                                                                                                                                                                                                                  |
| `search_plants`               | Read the current Plant catalog by name or code, accessible matches only. Call once with the user's name or code. If one result name equals the user's Plant name (any letter case), use it without asking. If the user gives only the end of a code, such as P043 (a full code is NORTH-P043), search the digits, such as 043; if several codes match, show all and ask. Use for: a named Plant. Not for: all Plants - use list\_accessible\_plants. Next: get\_plant\_overview. Read-only.                                                                                                       |
| `get_plant_overview`          | Read current identity, timezone, location (latitude, longitude), capacity (capacityKwp), and country for one accessible Plant; a field is absent when the Plant record has none. Use for: Plant scope, local dates, and Plant location. Not for: live status - use get\_plant\_dashboard. Next: get\_plant\_daily\_performance. Read-only.                                                                                                                                                                                                                                                        |
| `list_devices`                | Read the current device catalog for one Plant, all devices or one type. Use for: IDs, parents, types, and unclear names with nameQuery. nameQuery matches name or label; letter case and separators are ignored. If no device matches, call again without nameQuery to find similar names or labels. If no device or more than one device matches, stop. Show name, label, and type, and ask which device. Do not read data for all matches. Not for: offline status - use get\_plant\_dashboard. Next: query\_device\_telemetry. Read-only.                                                      |
| `get_plant_daily_performance` | Read stored daily yield, PR, availability, and irradiation for one Plant, up to 366 days; can lag. A plain-date end (YYYY-MM-DD) includes that whole day. With offset timestamps, start is inclusive and end is exclusive. Use for: low PR and daily performance. Not for: other stored daily values - use query\_plant\_daily. Next: get\_string\_daily\_analytics. Read-only.                                                                                                                                                                                                                   |
| `query_plant_5min`            | Read stored five-minute Plant values; can lag. Up to 31 days, but 1,000 rows allow about 3 days for one metric or 1 day for 3 metrics. start inclusive, end exclusive, with offsets. Use for: numbers across days. Not for: a one-day chart - use get\_plant\_chart. Next: query\_inverter\_daily. Read-only.                                                                                                                                                                                                                                                                                     |
| `query_plant_daily`           | Read stored daily Plant values, up to 366 days and 1,000 rows; can lag. start inclusive, end exclusive, with offsets. Use for: curtailment, soiling, revenue, and monthly values. Not for: yield, PR, availability, irradiation - use get\_plant\_daily\_performance. Next: query\_inverter\_daily. Read-only.                                                                                                                                                                                                                                                                                    |
| `list_alarms`                 | Read live ThingsBoard alarm state for one Plant, the same list as the GUI alarm page. Ten events per page; page 0 is the first page. Start inclusive and end exclusive on creation time, with UTC offsets. Use for: active alarms and alarm history. Not for: work orders - this connector cannot read them. Next: get\_alarm for one alarm, then query\_device\_telemetry for the device curve at the alarm time. Read-only.                                                                                                                                                                     |
| `get_alarm`                   | Read live ThingsBoard lifecycle state for one alarm in one Plant, from the same source as the GUI alarm page. Times are epoch milliseconds. A read does not acknowledge or clear the alarm. Use for: alarm details and lifecycle times. Not for: work orders - this connector cannot read them. Next: query\_device\_telemetry for the device curve at the alarm time. Read-only.                                                                                                                                                                                                                 |
| `query_string_5min`           | Read stored string Idc and Udc at 5 to 60 minutes; can lag. Up to 7 days, 1,000 rows; inverterIds optional. Data is kept for about the last 72 days only. For an older date, do not call; tell the user stored five-minute string data is not kept for that date. A plain-date end (YYYY-MM-DD) includes that whole day. With offset timestamps, start is inclusive and end is exclusive. Use for: current and voltage across days. Not for: a live curve today - use query\_device\_telemetry. Next: get\_plant\_dashboard. Read-only.                                                           |
| `query_inverter_daily`        | Read stored inverter daily values as reported; can lag. Up to 366 days, 1,000 rows. inverterIds optional. A plain-date end (YYYY-MM-DD) includes that whole day. With offset timestamps, start is inclusive and end is exclusive. Use for: yield, availability, and losses across inverters. Not for: a live device curve today - use query\_device\_telemetry. Next: query\_string\_5min. Read-only.                                                                                                                                                                                             |
| `get_plant_dashboard`         | Read live and today status for one Plant and its devices. Use for: production KPIs, offline devices, and disconnected strings. Not for: past daily performance - use get\_plant\_daily\_performance. Next: list\_devices. Read-only.                                                                                                                                                                                                                                                                                                                                                              |
| `get_portfolio_dashboard`     | Read live and today screens across accessible Plants, with 7-day yield and bounded alarm status. Pass plantIds to narrow it. Use for: Plants with problems today. Not for: one Plant over past days - use get\_plant\_daily\_performance. Next: get\_plant\_dashboard. Read-only.                                                                                                                                                                                                                                                                                                                 |
| `get_plant_chart`             | Read a Plant chart for one Plant-local day, live and today data, at 1 to 60 minutes. Use for: a one-day power, yield, or performance chart. Not for: stored numbers across days - use query\_plant\_5min. Next: query\_device\_telemetry. Read-only.                                                                                                                                                                                                                                                                                                                                              |
| `query_device_telemetry`      | Read telemetry for one device and one Plant-local day, today up to the last completed bucket or a past day. Keys are exact and case-sensitive and differ by device type; do not guess a spelling. A key with no points does not mean the device has no data. When a key has no points, the reply lists the device's keys and a suggested spelling. Missing buckets are null, never zero or a previous value. Get the device ID from list\_devices. Use for: device values at a time of day. Not for: string values across days - use query\_string\_5min. Next: get\_plant\_dashboard. Read-only. |
| `get_string_daily_analytics`  | Read stored daily string analytics for one Plant, latest processed day or one past Plant-local date; can lag. Call a string weak only with the peer value it was compared with; state that value. Use for: weak strings and peer ranks. Not for: current and voltage curves - use query\_string\_5min. Next: query\_string\_5min. Read-only.                                                                                                                                                                                                                                                      |

If the tab shows other tools, the connection reached a non-production server. Check the URL.

[![MCP Inspector Tools tab showing the production SolarSENS tools](/assets/images/connected-tools-real-3ba6b046730441d563ecae1dc2605f06.png)](https://ai.solarsens.co/assets/images/connected-tools-real-3ba6b046730441d563ecae1dc2605f06.png)

## Run search\_plants

1. Select `search_plants` in the Tools tab.
2. Enter a query, for example part of a Plant name or code.
3. Run the tool.

The result panel lists matching Plant IDs your account can access.

[![MCP Inspector search\_plants result panel showing a matched Plant ID](/assets/images/search-result-real-19536e22b1eb673ba75433e2cde673b1.png)](https://ai.solarsens.co/assets/images/search-result-real-19536e22b1eb673ba75433e2cde673b1.png)

A query with no match returns an empty result. This is not an error. A Plant outside your access never appears.

## If the connection fails

| What you see                                | What to check                                                           |
| ------------------------------------------- | ----------------------------------------------------------------------- |
| Inspector cannot reach the server           | Confirm the URL ends with `/mcp` and that you chose the HTTP transport. |
| The sign-in page returns an error           | See [Help](https://ai.solarsens.co/docs/troubleshooting.md).            |
| The connection succeeds but no tools appear | Ask AVA Asia to check the SolarSENS account-to-Plant mapping.           |
