# Connect Claude Code and other clients

> Connect Claude Code, or any other MCP client, to a Signalbox workspace. Sign in with Signalbox, or send an API key.

There are two ways to sign an agent in. Use the first where your client supports it.

| Way | Works with | The agent's level comes from |
|---|---|---|
| Sign in with Signalbox (OAuth) | Clients that can sign in to a remote MCP server, such as Claude Code | What you pick when you approve |
| API key | Any client that can send a header | The key |

## Claude Code, by signing in

1. In Signalbox, open **Agents** and copy **This workspace's address**. It looks like `https://api.trysignalbox.com/t/{workspace id}/mcp`.
2. Add it to Claude Code:

```bash
claude mcp add --transport http signalbox https://api.trysignalbox.com/t/{workspace id}/mcp
```

3. In Claude Code, run `/mcp` and sign in. Your browser opens Signalbox.
4. Pick a level, choose whether the agent may read leads, and approve.

## Any client, by API key

1. In Signalbox, open **API keys** and make a key. Only a workspace admin can. Copy it then: the full key is shown once.
2. Give your client the address and the key, in the `x-api-key` header.

In Claude Code:

```bash
claude mcp add --transport http signalbox https://api.trysignalbox.com/mcp --header "x-api-key: YOUR_API_KEY"
```

The key names the workspace, so the plain `/mcp` address is enough.

For another client, look in its own documentation for how to add a remote MCP server with a header. It needs two things:

| Setting | Value |
|---|---|
| Address | `https://api.trysignalbox.com/mcp` |
| Header | `x-api-key`, with your key as its value |

Keep the key out of anything you share or commit. See [Authentication](/api/authentication/) for what a key may do.

## The skills in Claude Code

Any agent can read the skills through the server, with `get_skill`. Claude Code can also load them as a plugin, so it picks the right skill by itself.

The plugin is the `agent-plugin` folder of the Signalbox repository. With a copy of that folder:

```bash
claude --plugin-dir /path/to/agent-plugin
```

It holds the four skills: `build-a-flow`, `set-up-workspace`, `explain-a-lead` and `review-a-flow`. They are the same files the server gives out.

## Which to choose

- **Sign in** when a person is at the keyboard. The connection is yours, it shows on the Agents page, and **Disconnect** stops it at once.
- **A key** for a client that cannot sign in, or one that runs with nobody there. Delete the key on the API keys page to stop it.

## What the agent should do first

Every client should call `get_started` first. It gives the rules, the state of the workspace and what to do next.