# Skill: Connect SolarSENS to This AI

You are helping the user connect the AI tool they use to SolarSENS through
the SolarSENS MCP server. When you finish, the user can ask about their solar
Plants in plain words and get answers from SolarSENS monitoring data.

The connection is read-only. It returns only the Plants that the user's
SolarSENS account can see.

Server URL, always exactly:

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

## Step 1: Gather context

Read the SolarSENS AI homepage and the getting-started page:

- https://ai.solarsens.co/
- https://ai.solarsens.co/docs/intro

## Step 2: Find out where you are running

Decide which client the user wants to connect. Use what you already know from
the conversation and your own runtime. Ask only when you cannot tell.

| Client | Who does the setup | Guide |
| --- | --- | --- |
| Claude Code | You run the commands | https://ai.solarsens.co/docs/installation/claude-code |
| OpenCode | You run the commands | https://ai.solarsens.co/docs/installation/opencode |
| ChatGPT | The user clicks through Settings; you guide them | https://ai.solarsens.co/docs/installation/chatgpt |
| Claude Desktop | The user clicks through Settings; you guide them | https://ai.solarsens.co/docs/installation/claude-desktop |
| Another MCP client | Use its native remote MCP + OAuth flow | https://ai.solarsens.co/docs/intro |

Read the guide for the chosen client before you act. The guide is the source
of truth when it differs from this file.

## Step 3: Add the server

### Claude Code

```bash
claude mcp add --transport http solarsens https://mcp.solarsens.co/mcp
```

This saves the server. It does not sign the user in.

### OpenCode

From the user's project folder:

```bash
opencode mcp add solarsens --url https://mcp.solarsens.co/mcp
```

This writes a `solarsens` entry to `opencode.json`. Keep only that entry. Do
not add a `workers.dev` URL, a `solarsens-preview` server, or a fixture token.

### ChatGPT or Claude Desktop

You cannot change these settings yourself. Give the user the steps from the
guide, one at a time, and wait for them to confirm each one:

- ChatGPT: **Settings** or **Apps and Connectors** → **Add connector** → name
  `SolarSENS` → the server URL → **OAuth**.
- Claude Desktop: **Settings** → **Connectors** → **Add custom connector** →
  name `SolarSENS` → the server URL → save.

## Step 4: Sign in

The user signs in with their own SolarSENS account in a browser and approves
the read-only connection.

- Claude Code: `claude mcp login solarsens`, or `/mcp` in a session and select
  `solarsens`. Over SSH, Claude Code prints a URL; the user opens it on a
  machine with a browser and pastes the redirect URL back.
- OpenCode: `opencode mcp auth solarsens`. It uses a loopback callback on port
  19876. If sign-in fails because that port is in use, follow
  https://ai.solarsens.co/docs/troubleshooting
- ChatGPT and Claude Desktop open the sign-in page when the user saves the
  connector.

## Step 5: Check the connection

1. Confirm the server is connected:
   - Claude Code: `claude mcp list` shows `solarsens` as `✔ Connected`.
   - OpenCode: `opencode mcp list` no longer shows `needs authentication`.
   - ChatGPT and Claude Desktop: the connector list shows **Connected**.
2. List the SolarSENS tools. Expect exactly 4 read-only tools:
   `list_accessible_plants`, `search_plants`, `get_plant_overview`, and
   `get_performance`. Some clients need a new session before
   the tools appear.
3. Call `list_accessible_plants` and show the user the Plants it returns.
4. Suggest one next question, for example:
   `For the Plant you found, show yesterday's performance, with the timezone and data coverage.`

If the connection works but no Plant is returned, the account has no Plant
access yet. Tell the user to ask their SolarSENS administrator. Do not try
other Plant IDs.

## Step 6: Report

Finish with a short checklist:

- Client connected
- Sign-in completed (yes/no)
- Tools found (expect 4)
- Plants returned (names or count), or "none: contact administrator"
- One suggested first question

## Important rules

- Never ask the user to paste a SolarSENS password, access token, or client
  secret into the chat or into a file. Sign-in happens only in the browser.
- Never invent credentials, Plant IDs, or telemetry values.
- Use only `https://mcp.solarsens.co/mcp`.
- The connection is read-only. It cannot change settings, devices, or records.
  It cannot read devices, alarms, work orders, or portfolios yet.
- A missing value is not zero production. Report coverage and warnings as the
  tool returns them.
- For any error, read https://ai.solarsens.co/docs/troubleshooting and
  https://ai.solarsens.co/docs/reference/limits-and-errors before you retry.