> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sensorup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Install the Studio command-line tool and Claude connector

> Run the Studio command-line tool (sustudio) and the Studio connector for Claude (sustudio-mcp) on macOS, Linux or Windows.

SensorUp Studio has two tools you can run from your own computer:

* **The Studio command-line tool** (`sustudio`). It works with Studio from a terminal. Every Studio module's actions are commands, and each action answers in JSON.
* **The Studio connector for Claude** (`sustudio-mcp`). It lets Claude use one Studio module's actions for you.

You do not install anything by hand. Both run through `npx`, which comes with Node.js.

## Before you start

You need:

* **Node.js 24 or newer.** Check with `node --version`.
* **A Studio account.**
* **Your Studio address.** Use the address you sign in to Studio at in your browser. For example: `https://studio.us.sensorup.com`.

> [!NOTE]
>
> There is no default Studio address. Replace `<your Studio address>` in every command below with your own.

## Pick your system

Follow the tab for your system from top to bottom.

> [tab] macOS
>
> **1. Open Terminal and check Node.js**
>
> ```bash theme={null}
> node --version
> ```
>
> The version must start with `v24` or higher. If it does not, install the current Node.js from [nodejs.org](https://nodejs.org).
>
> **2. Sign in to the command-line tool**
>
> ```bash theme={null}
> npx @sensorup/sustudio login --base-url <your Studio address>
> ```
>
> The first time, `npx` asks `Ok to proceed? (y)`. Answer `y`. See [Sign in](#sign-in-with-the-command-line-tool) for what happens next.
>
> **3. Run a first command**
>
> ```bash theme={null}
> npx @sensorup/sustudio whoami
> ```
>
> A working sign-in shows `"session": "active"`. If it shows `expired`, run any command: the tool renews the sign-in by itself for up to 8 hours.
>
> **4. Add the connector to Claude Code, or to Claude Desktop**
>
> For Claude Code, run:
>
> ```bash theme={null}
> claude mcp add --transport stdio --scope user sustudio-assets -- npx -y @sensorup/sustudio-mcp assets --base-url <your Studio address>
> ```
>
> For Claude Desktop, open `~/Library/Application Support/Claude/claude_desktop_config.json` and add the entry shown in [Claude Desktop](#claude-desktop). Then restart Claude Desktop.

> [tab] Linux
>
> **1. Open a terminal and check Node.js**
>
> ```bash theme={null}
> node --version
> ```
>
> The version must start with `v24` or higher. If it does not, install the current Node.js from [nodejs.org](https://nodejs.org).
>
> **2. Sign in to the command-line tool**
>
> ```bash theme={null}
> npx @sensorup/sustudio login --base-url <your Studio address>
> ```
>
> The first time, `npx` asks `Ok to proceed? (y)`. Answer `y`. See [Sign in](#sign-in-with-the-command-line-tool) for what happens next.
>
> **3. Run a first command**
>
> ```bash theme={null}
> npx @sensorup/sustudio whoami
> ```
>
> A working sign-in shows `"session": "active"`. If it shows `expired`, run any command: the tool renews the sign-in by itself for up to 8 hours.
>
> **4. Add the connector to Claude Code, or to Claude Desktop**
>
> For Claude Code, run:
>
> ```bash theme={null}
> claude mcp add --transport stdio --scope user sustudio-assets -- npx -y @sensorup/sustudio-mcp assets --base-url <your Studio address>
> ```
>
> For Claude Desktop, open `~/.config/Claude/claude_desktop_config.json` and add the entry shown in [Claude Desktop](#claude-desktop). Then restart Claude Desktop.

> [tab] Windows
>
> Use Command Prompt: open the Start menu, type `cmd`, and press Enter. Do not use PowerShell: with its default settings on Windows it refuses to run `npx`.
>
> **1. Open Command Prompt and check Node.js**
>
> ```bat theme={null}
> node --version
> ```
>
> The version must start with `v24` or higher. If it does not, install the current Node.js from [nodejs.org](https://nodejs.org).
>
> **2. Sign in to the command-line tool**
>
> ```bat theme={null}
> npx @sensorup/sustudio login --base-url <your Studio address>
> ```
>
> The first time, `npx` asks `Ok to proceed? (y)`. Answer `y`. See [Sign in](#sign-in-with-the-command-line-tool) for what happens next.
>
> **3. Run a first command**
>
> ```bat theme={null}
> npx @sensorup/sustudio whoami
> ```
>
> A working sign-in shows `"session": "active"`. If it shows `expired`, run any command: the tool renews the sign-in by itself for up to 8 hours.
>
> **4. Add the connector to Claude Code, or to Claude Desktop**
>
> For Claude Code, run:
>
> ```bat theme={null}
> claude mcp add --transport stdio --scope user sustudio-assets -- cmd /c npx -y @sensorup/sustudio-mcp assets --base-url <your Studio address>
> ```
>
> On Windows, `cmd /c` goes in front of `npx`. Claude starts the connector by itself, and on Windows it can only start `npx` this way.
>
> For Claude Desktop, open `%APPDATA%\Claude\claude_desktop_config.json` and add the Windows entry shown in [Claude Desktop](#claude-desktop). Then restart Claude Desktop.

## The command-line tool

Run the tool with `npx`:

```bash theme={null}
npx @sensorup/sustudio --help
```

Each Studio module has its own commands. To see what a module offers, run:

```bash theme={null}
npx @sensorup/sustudio <module> --help
```

### Sign in with the command-line tool

You sign in once:

```bash theme={null}
npx @sensorup/sustudio login --base-url <your Studio address>
```

The command prints a one-time code and a link. Open the link in the browser where you are signed in to Studio. Check that the code matches, then approve it.

You stay signed in on that computer for up to 8 hours. After that, sign in again. To sign out sooner, run `npx @sensorup/sustudio logout`.

If you run a command before you have given the tool an address, it stops and names the sign-in command to run.

## The Studio connector for Claude

The connector serves one Studio module. To use several modules, add one entry for each. For example, add `assets` and `datasets` as two entries.

Each entry carries your Studio address.

### Claude Code

One command adds the connector for all your projects:

```bash theme={null}
claude mcp add --transport stdio --scope user sustudio-assets -- npx -y @sensorup/sustudio-mcp assets --base-url <your Studio address>
```

On Windows, put `cmd /c` in front of `npx`:

```bat theme={null}
claude mcp add --transport stdio --scope user sustudio-assets -- cmd /c npx -y @sensorup/sustudio-mcp assets --base-url <your Studio address>
```

To add another module, change the entry name and the module name. For example, `sustudio-datasets` and `datasets`.

### Claude Desktop

Add an entry to the `mcpServers` section of Claude Desktop's settings file:

```json theme={null}
{
  "mcpServers": {
    "sustudio-assets": {
      "command": "npx",
      "args": ["-y", "@sensorup/sustudio-mcp", "assets", "--base-url", "<your Studio address>"]
    }
  }
}
```

On Windows, the entry starts `npx` through `cmd`:

```json theme={null}
{
  "mcpServers": {
    "sustudio-assets": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "@sensorup/sustudio-mcp", "assets", "--base-url", "<your Studio address>"]
    }
  }
}
```

The settings file is here:

| System | File |
| - | - |
| macOS | `~/Library/Application Support/Claude/claude_desktop_config.json` |
| Windows | `%APPDATA%\Claude\claude_desktop_config.json` |
| Linux | `~/.config/Claude/claude_desktop_config.json` |

Quit Claude Desktop completely and start it again after you edit the file.

### Sign in from Claude

You do not need a terminal for this step. In Claude, ask it to sign you in to Studio. Claude shows a link and a one-time code. Open the link in the browser where you are signed in to Studio, check that the code matches, and approve it.

You stay signed in for up to 8 hours, also when the connector restarts. After that, ask Claude to sign you in again.

> [!NOTE]
>
> Claude on the web cannot run a connector on your computer. Use Claude Code or Claude Desktop.

## If something goes wrong

### "no Studio address is configured"

The tool or connector does not know which Studio to talk to. Fix it in one of two ways:

* Add `--base-url <your Studio address>` to the connector's entry in your Claude settings. Then start the connector again.
* Run the sign-in command: `npx @sensorup/sustudio login --base-url <your Studio address>`.

### The connector's address differs from the saved one

The message says the address in the connector's entry differs from the address the saved profile uses. Fix it in one of two ways:

* Change the address in the connector's entry to the address the message names.
* Give the connector a different profile name. Set `SUSTUDIO_PROFILE` in the entry to a new name. In Claude Desktop, add it under `"env"` in the entry. In Claude Code, add `--env SUSTUDIO_PROFILE=<a new name>` to the `claude mcp add` command, right after the entry name.

### Node.js is too old

If `node --version` shows a version below 24, install the current Node.js from [nodejs.org](https://nodejs.org). Then open a new terminal and run the command again.

## Where your settings live

The tools keep your saved Studio address and sign-in in `~/.config/sustudio/`. On Windows, this is the `.config\sustudio` folder in your user folder.

## What is coming

Signed downloads, and a Homebrew install for people without Node.js, are planned separately.
