---
title: Connecting your assistant
description: Add Signal's connector to Claude, ChatGPT, Claude Code, Cursor or VS Code, then sign in and approve it.
product: signal
section: mcp
order: 2
---

# Connecting your assistant

## Before you start

- The connector is included on every Signal plan.
- A workspace admin decides whether assistants may be used in the workspace at all, and how much they may do. See [Admin controls](admin-controls.md).
- Each person connects their own assistant, with their own Signal sign-in.
- Any assistant that can add a remote MCP connector with sign-in (OAuth) can connect. The steps for the most common ones are below.

## The connector URL

```text
https://crm.empiraa.app/mcp
```

You can also copy it in Signal: select **Connect AI** in the top bar, or open **Settings › Integrations › AI assistants**.

## Claude on the web

1. In Claude, open **Connectors** (in Settings, or under Customize) and choose **Add custom connector**.
2. Name it **Empiraa Signal** and paste the connector URL.
3. Select **Add**, then **Connect**, and sign in to Signal when it asks.
4. Approve the connection on Signal's screen.

On a Claude Team or Enterprise plan, an admin of your Claude organization adds the connector for everyone first. You then find it under Connectors and select **Connect**.

## Claude desktop

1. Connectors you add in Claude on the web are in Claude desktop too, when you're signed in to the same Claude account.
2. To add it in the app instead, open **Settings › Connectors**, choose **Add custom connector**, and follow the steps for Claude on the web.
3. If a chat doesn't reach Signal, check that Empiraa Signal is turned on for that chat.

## ChatGPT on the web

1. In ChatGPT on the web, turn on **Developer mode** in Settings.
2. Create a new app or connector, name it **Empiraa Signal** and paste the connector URL.
3. If it asks how to sign in, choose **OAuth**. Create it, then sign in to Signal when it asks.
4. Approve the connection on Signal's screen.

On a ChatGPT Business or Enterprise workspace, an admin may need to allow Developer mode or add the app for you.

## ChatGPT desktop

1. Add Empiraa Signal in ChatGPT on the web first, as above.
2. It's then in the ChatGPT desktop app too, when you're signed in to the same ChatGPT account.

## Claude Code

1. Add Signal from a terminal:

   ```bash
   claude mcp add --transport http signal https://crm.empiraa.app/mcp
   ```

2. Start Claude Code, type `/mcp`, choose **signal** and select **Authenticate**. Your browser opens Signal.
3. Sign in if asked, and approve the connection on Signal's screen.

## Cursor

1. Open Cursor Settings, go to **MCP** (Tools & Integrations) and add a new MCP server. Cursor opens its `mcp.json` file.
2. Add Signal and save:

   ```json
   {
     "mcpServers": {
       "signal": { "url": "https://crm.empiraa.app/mcp" }
     }
   }
   ```

3. Back in Cursor Settings, select the sign-in button beside **signal**. Your browser opens Signal, where you approve the connection.

## VS Code with GitHub Copilot

1. Open the Command Palette and run **MCP: Add Server**.
2. Choose **HTTP**, paste the connector URL and name it `signal`. Or add it to `.vscode/mcp.json`:

   ```json
   {
     "servers": {
       "signal": { "type": "http", "url": "https://crm.empiraa.app/mcp" }
     }
   }
   ```

3. When VS Code asks to sign in, allow it, then approve the connection on Signal's screen.
4. In the chat, choose **Agent** mode. Signal's tools are in its tools list.

Each app's menus change from time to time. If a step reads differently, look for the app's connector or MCP settings.

## Other MCP clients

Any client that supports MCP's streamable HTTP transport and its OAuth authorization flow can connect. It finds Signal's sign-in endpoints itself from the connector URL and registers itself, so there's no client id to request. The details are in [How it works](how-it-works.md).

## Approving the connection

When your assistant sends you to Signal, sign in if asked. Signal shows which app is asking and who you're signed in as, with **Verified** beside an app Signal has confirmed, such as Claude or ChatGPT. Then choose:

- **Workspace:** the one the assistant works in when you don't name another.
- **Access:** **View only**, or **View and make changes** (offered when the app asks to make changes).
- **Areas it can use:** the parts of Signal it may reach, ticked for your role. Change them as you like.

Select **Approve** to connect, or **Deny** if you didn't expect the request.

### View only, or View and make changes

- **View only:** it can read what you can see in Signal. It isn't shown the tools that make changes at all, and the buttons on its interactive cards that would change something are turned off.
- **View and make changes:** it can also create and update records, always as you. Each change is shown as a card first, and your assistant app asks you before applying it, unless you've told it to always allow Signal's changes.

To change an app's access or areas, disconnect it and connect it again. Going from View only to making changes always needs a fresh approval, so a connection can't gain write access quietly.

### Areas

An assistant reaches only the areas you tick when you approve it:

| Area | What it covers |
|---|---|
| **Sales** | Prospect contacts, Accounts, Deals, Actions and Segments |
| **Marketing** | Campaigns, Sequences, Forms and email results |
| **Analytics** | Dashboards, reports and forecasts |
| **Data import** | Bringing records into Signal from files and other tools |

Every connection can also look up who you are, your workspaces, Signal's help and your connected apps, and open one record by its id.

The first ticks follow your role: admins and managers get all four. Everyone else gets Sales and Analytics, plus Marketing when their role has Marketing access.

## Your first prompts

After you connect, Signal suggests three first prompts built from your own work, for example "Catch me up on *your largest open Deal* before my next call". Ready-made prompts such as **My Morning Brief** also appear in assistants that show prompts. See [Prompts, resources and widgets](prompts-resources-widgets.md).

## Disconnecting

- **Your connected apps**, in **Settings › Integrations › AI assistants**, lists each app you've connected, with its access, areas, default workspace and when it was last used. **Disconnect** ends its access straight away.
- Workspace admins also see **Members' connections**, and can disconnect an app for a member. That ends its access for them in every workspace.
- Changing or resetting your Signal password disconnects your apps. If you're removed from a workspace, assistants can no longer reach it.
- Signal pauses an app that makes an unusual number of changes or errors. Select **Resume** beside it if you expected that.