---
title: "Connect Claude"
description: "Connect FullHouse to Claude on the web and desktop, and to Claude Code, step by step."
---

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

# Connect Claude

Use this page to connect Claude to your FullHouse workspace. In Claude on the web and desktop you add FullHouse as a custom connector. In Claude Code you add it with one command.

Before you start, check that your plan [includes MCP](/mcp) and copy the **Server URL** from **Workspace → MCP server**. It looks like this:

```text
https://app.meetfullhouse.com/mcp
```

## Which Claude should you use?

| | Best for | Can it upload a file from your computer? |
| --- | --- | --- |
| **Claude on the web or desktop** | Writing, setup, questions and reports | Not by itself. [Upload in Media](/workspace/media-library) first, then ask Claude to use the file. |
| **Claude Code** | The same jobs, plus uploading large videos and working with files on your computer | Yes. It can run the upload for you. See [Upload a video](/mcp/what-it-can-do). |

## Connect Claude on the web or desktop

You add the connector once and it belongs to your Claude account, so you don't need to edit any configuration file on your computer.

1. **Open Claude's connector settings**

   Sign in to Claude on the web or desktop and find **Connectors**, under **Customize** or **Settings** depending on your version. Claude moves these menus from time to time, so look in both.
2. **Add a custom connector**

   Choose to add a connector, then **Add custom connector**.
3. **Enter FullHouse's details**

   Name it `FullHouse` and paste the server URL.
4. **Keep the sign-in options**

   If Claude asks how to sign in, choose an option that signs you in, and keep its recommended option for the OAuth client. Leave any request headers empty, because you don't need a token here.
5. **Sign in and allow access**

   Select **Connect** if it's offered. FullHouse opens in your browser. Sign in if asked, choose **Full access** or **Read only**, then select **Allow access**. See [the approval screen](#the-approval-screen) for what each part means.
6. **Turn it on in a chat**

   In a conversation, open the **+** menu, choose **Connectors** and turn on FullHouse.
7. **Test it**

   Ask something that changes nothing: `Use FullHouse to list my webinars.`

For the current steps on Claude's side, see Anthropic's guide to [custom connectors using remote MCP](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).

### Things that depend on your Claude plan

- **Free:** Anthropic limits Free accounts to one custom connector.
- **Team and Enterprise:** an organization owner, or someone with the right admin role, adds the connector under the organization's settings. Each person then connects it from their own connector list and signs in to their own FullHouse account.

### Use it on mobile

Add the connector on the web or desktop first. Once it's added, it also works in the Claude mobile app, because the connection belongs to your Claude account rather than to one device.

### Decide what Claude can do without asking

Claude asks for your approval before using a tool. You can usually approve once or choose **Allow always**. A sensible setup is:

- Use **Allow always** for tools that only read, such as `list_webinars` or `get_webinar_report`.
- Keep approving one at a time for anything that deletes, publishes or sends, such as `delete_webinar`, `delete_registrant`, `publish_webinar` or `add_registrant`.

Anthropic also warns that research mode can use connector tools without further approval, so turn off tools that make changes before you use it. See [Security](/mcp/security) for how approvals and FullHouse's own safeguards fit together.

## Connect Claude Code

Claude Code runs in your terminal or editor. Run these commands in your terminal, or ask someone comfortable with the terminal to set it up once.

### Sign in (recommended)

1. **Add the server**

```bash
claude mcp add --transport http fullhouse https://app.meetfullhouse.com/mcp
```

By default this applies only to the project folder you're in. To use FullHouse from every folder, add `--scope user` after `--transport http`.
2. **Sign in**

Start Claude Code with `claude`, then run `/mcp`. Choose `fullhouse` and follow the sign-in steps. Your browser opens FullHouse, where you choose the access level and select **Allow access**.
3. **Test it**

Ask Claude Code: `Use FullHouse to list my webinars.`
### Access token

Use this if you can't complete the browser sign-in, for example on a remote machine.

1. **Create a token**

In **Workspace → MCP server**, select **New access token**. See [Create an access token](/mcp) for the options.
2. **Add the server with the token**

```bash
claude mcp add --transport http fullhouse https://app.meetfullhouse.com/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"
```

Replace `YOUR_TOKEN` with your token. While the new token message is on screen, the **Claude Code** tab shows this command with your token already filled in.
3. **Check it**

Run `claude mcp list`. FullHouse should show as connected. A wrong token shows up as a failed connection, because the add command doesn't test it.

:::caution
Don't use `--scope project` with a token. That setting saves the server to a file meant to be shared with your team through version control, which would share your token too.
:::

Anthropic's [Claude Code MCP guide](https://code.claude.com/docs/en/mcp) has more options.

### Remove it from Claude Code

```bash
claude mcp logout fullhouse
claude mcp remove fullhouse
```

Then check **Workspace → MCP server** and disconnect or revoke anything left in the list. A token keeps working until you revoke it in FullHouse, even after you remove it from Claude Code.

## The approval screen

Every app that signs in reaches this FullHouse screen. It says "[App] wants to access [your workspace]" and you decide what happens next.

| Part of the screen | What it means |
| --- | --- |
| **Returns you to claude.ai** (or another address) | Where you go after approving. A green tick means FullHouse recognises the address as a known AI tool: Claude, ChatGPT, VS Code or Cursor. |
| **Returns you to an app on this computer** | The app runs on your own machine, as Claude Code and many editors do |
| **App details from [address]** | The website that published the app's name and details, when it differs from the address above |
| **Full access** | "Read and make changes for you." This is selected by default. |
| **Read only** | "Look things up and report, but change nothing." |
| **It will be able to** | The exact list for the option you picked (see below) |
| **Signed in as [email]. Not you?** | The FullHouse account being connected. **Not you?** signs you out so you can use another account. |
| **Cancel** | Refuses access and returns you to the app |
| **Allow access** | Approves the connection |

With **Read only**, the app can:

- See your webinars, challenges and their settings
- See registrants, attendance, questions and reports

With **Full access**, it can also:

- Create, edit, publish, pause and delete webinars and challenges
- Change schedules, emails, offers, polls and automations
- Register, unsubscribe and delete registrants
- Reply to questions and post in live chat

The screen also reminds you that the app never sees your password or payment details, and that you can disconnect it at any time under **Workspace → MCP server**.

If an app asks only for read access, you won't see the access choice. It gets **Read only**, and the list shows only what that allows.

### If you aren't signed in

FullHouse sends you to sign in first, then brings you back to this screen. If you take longer than 30 minutes you land on your dashboard instead, so start connecting again from your AI tool. If your email address isn't verified yet, FullHouse asks you to verify it first. After that, start connecting again.

### Messages on this screen

| Message | What it means | What to do |
| --- | --- | --- |
| "FullHouse can't verify this app's name. Only continue if you started connecting from [app] just now." | The app registered itself and its address isn't one FullHouse recognises. This is normal for some desktop tools. | Continue only if you started the connection yourself a moment ago. If you didn't, select **Cancel**. |
| **MCP isn't included in your [plan] plan** | Your plan doesn't include MCP. Only **Go back** is offered. | Move to a plan with MCP access |
| **This workspace is suspended** | "Apps can't be connected while it's suspended." | Contact support |
| **This connection can't continue**: "This app isn't registered with FullHouse. Remove the connection in the app and add it again." | The app's registration is no longer known. | Remove FullHouse from your AI tool and add it again |
| **This connection can't continue**: "[App] asked to send you to an address it hasn't registered, so FullHouse stopped here." | The app asked to return you somewhere it hadn't declared. FullHouse stops as a safety measure. | Add the connection again from the app. If it keeps happening, don't continue, and contact the app's maker. |
| **This connection can't continue**: "The app didn't say where to return you after approving." or "The app didn't send a valid client_id." | The app's request was incomplete. | Start connecting again from the app |
| **This connection can't continue**: "The app's metadata at [address] can't be used…" | FullHouse couldn't read valid details from the app's website. | Try again later, or contact the app's maker |
| "FullHouse is busy. Try again in a moment." | A temporary problem | Try again |

If your AI tool reports "This approval code has expired. Connect again.", the approval took too long to finish. Approvals last 10 minutes. Start again from the tool.

For problems after you've connected, see [If something goes wrong](/mcp).

Source: https://docs.meetfullhouse.com/mcp/connect-claude/index.mdx