# Add Heatsink to your agent

## What your agent can do in Heatsink

Any agent that supports MCP can design and edit the themes on your case screen and read your PC's sensors. Your agent does the thinking on its own model and plan, and Heatsink's 22 tools carry out what it asks.

- **Themes.** List your themes, read one in full, create a theme at your screen's exact size, and undo an edit by restoring an earlier revision.
- **Widgets.** Add, change, move, resize, restack and remove widgets, and bind a widget to a sensor reading. Your agent can draw its own gauges as SVG, and build segmented meters and image-per-state widgets.
- **Images.** Upload a picture to a theme, list a theme's pictures with their sizes, and delete one no widget uses.
- **Publishing.** Publish a draft so your screen shows it, or switch the screen to another published theme.
- **Sensor values.** Read the live readings and names from your most recently active PC, and check whether a PC is reporting.
- **Streams.** List your data streams, check one's status and data, and create, edit or delete streams built from the tools of MCP servers your PC has connected and opened to the agent.

The agent inside the Heatsink app uses the same tools, so what you can ask one you can ask the other. Nothing the agent does runs a command on your PC: it edits your account's themes and streams, and the app picks the changes up within a second or two while it runs.

## 1. Add Heatsink to your client

Every client uses the same address, `https://mcp.heatsink.io/mcp`. Clients register themselves without an API key, and most open a browser to sign you in on first use. **Settings → Agent** in the Heatsink app has these steps and snippets ready to copy.

### Claude (web and desktop app)

1. In Claude, open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.
2. Name it `Heatsink` and enter `https://mcp.heatsink.io/mcp` as the server URL.
3. Under **OAuth client**, leave **Use Claude's published identity** selected, then click **Add**.
4. Sign in to Heatsink when prompted.

On a Claude Team or Enterprise plan, an owner adds the connector under **Organization settings → Connectors**. Members then click **Connect** beside it.

### ChatGPT

1. Open [chatgpt.com/plugins](https://chatgpt.com/plugins), click **+**, then **Add custom MCP server**.
2. Name it `Heatsink` and enter `https://mcp.heatsink.io/mcp` under **Connection**. Leave OAuth as the authentication.
3. Accept the risk notice, then click **Create as a plugin**.
4. Sign in to Heatsink when prompted, and type `@Heatsink` in a new conversation to use it.

Under the plugin's **Permission** setting, **Allow low-risk tools** lets read-only tools run without a prompt.

### Claude Code

Run this in a terminal, and add `--scope user` to register it across all your projects. Then run `/mcp` in Claude Code and pick Heatsink to sign in.

```bash
claude mcp add --transport http heatsink https://mcp.heatsink.io/mcp
```

### Cursor

Add this to `~/.cursor/mcp.json`, or to `.cursor/mcp.json` in a project.

```json
{
  "mcpServers": {
    "heatsink": { "url": "https://mcp.heatsink.io/mcp" }
  }
}
```

### Codex

Run both commands in a terminal. Codex does not sign in on the first call, so the login command opens your browser.

```bash
codex mcp add heatsink --url https://mcp.heatsink.io/mcp
codex mcp login heatsink
```

### VS Code

Add this to `.vscode/mcp.json`, or to your user `mcp.json`.

```json
{
  "servers": {
    "heatsink": { "type": "http", "url": "https://mcp.heatsink.io/mcp" }
  }
}
```

### Gemini CLI

Run this in a terminal, and Gemini CLI opens a browser to sign you in on first use.

```bash
gemini mcp add --transport http heatsink https://mcp.heatsink.io/mcp
```

### Any other client

Add `https://mcp.heatsink.io/mcp` wherever your client lists remote servers. Your client must support streamable HTTP with OAuth 2.1, which signs you in through your browser.

## 2. Sign in and authorize

Signing in opens a **Connect to Heatsink** screen in your browser. Sign in with your Heatsink account, the same way you do in the app, including your second factor if you turned one on.

The screen names the app asking for access and the account you are signed in as. When the app publishes its identity, as Claude does, the screen also shows the app's web address, and it shows where your sign-in redirects when that is not your own computer. Click **Authorize** to connect. Only approve a connection you started yourself.

Your Heatsink password and sign-in methods are never shared with the app. It receives its own access to your account, which it renews while you keep using it.

## Managing access

A connection belongs to your Heatsink account, not to one PC. Theme edits land in your account, so every PC signed into it picks them up, and sensor readings come from whichever of your PCs reported most recently.

To cut an app off, open **Settings → Security → Authorized apps** in the Heatsink app and click **Revoke** beside it. The app can no longer renew its access, and loses it within the hour. Connect it again to restore it.