---
title: "Connect other AI tools"
description: "Connect FullHouse to ChatGPT, Cursor, VS Code, Codex and other MCP-compatible tools by signing in or using an access token."
---

> 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 other AI tools

FullHouse works with any AI tool that can connect to a remote MCP server over HTTP. Use this page to connect ChatGPT, Cursor, VS Code, Codex and similar tools.

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

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

## What every tool needs

Whatever the tool, the setup comes down to the same three choices:

| Setting | What to choose |
| --- | --- |
| **Address or URL** | The server URL above |
| **Connection type or transport** | **HTTP**, sometimes called "streamable HTTP" or "remote". Don't choose SSE, because FullHouse doesn't offer it. |
| **Authentication** | **OAuth** or "sign in" wherever it's offered. Use an [access token](/mcp) only if the tool has no sign-in option. |

When a tool signs in, you'll see the FullHouse [approval screen](/mcp/connect-claude), where you pick **Full access** or **Read only** and select **Allow access**.

A tool that can only run a local program on your computer can't connect to FullHouse directly, because FullHouse is a remote server. Check that your tool supports remote servers.

## Connect ChatGPT

ChatGPT connects from the web, and it needs the sign-in method.

1. **Find where custom servers are added**

   In ChatGPT on the web, look for the option to add a custom MCP server. It's usually under **Plugins**, using the **+** button and **Add custom MCP server**. If you don't see that, look in **Settings**. This area of ChatGPT has changed a few times.
2. **Enter FullHouse's details**

   Name it `FullHouse` and paste the server URL.
3. **Choose OAuth**

   Choose **OAuth** for authentication. Review OpenAI's risk warning and continue if you're happy to.
4. **Finish adding it**

   Complete the remaining steps ChatGPT shows. In the current flow you create it as a plugin, then install it before using it in a conversation.
5. **Sign in and allow access**

   Sign in to FullHouse when asked, choose the access level and select **Allow access**.
6. **Test it**

   In a new conversation, ask: `Use FullHouse to list my webinars.`

See OpenAI's guide to [adding a custom MCP server](https://developers.openai.com/api/docs/guides/custom-mcp-server) for the current steps.

### What depends on your ChatGPT plan

What you can do depends on your ChatGPT plan, and on some plans an admin has to set it up. OpenAI can change this. At the time of writing, OpenAI's [help article](https://help.openai.com/en/articles/12584461-developer-mode-and-mcp-apps-in-chatgpt) says full support is for Business, Enterprise and Edu on the web, while Pro can connect custom servers with read and fetch permissions only. On Business, Enterprise and Edu, an admin may need to create the connection or give you permission.

If your plan only allows read and fetch, you can still search and look things up in FullHouse, using the `search` and `fetch` tools. To make changes from ChatGPT, you'd need a plan that allows them, or you can use a different AI tool.

### Approving changes in ChatGPT

OpenAI's guide says ChatGPT asks you to confirm any action that isn't marked read-only, and shows you the details before you approve. FullHouse marks its read-only tools, so looking things up shouldn't need the same confirmation as making changes. You can choose to remember a decision for a tool within a conversation, but do this only for tools you're happy to run unattended.

## Connect Cursor

Cursor keeps its servers in a settings file. Use `~/.cursor/mcp.json` in your home folder to use FullHouse in every project, or `.cursor/mcp.json` in one project. You can turn servers on or off in Cursor's settings.

Add FullHouse like this:

```json
{
  "mcpServers": {
"fullhouse": {
  "url": "https://app.meetfullhouse.com/mcp"
}
  }
}
```

Cursor then offers to sign you in, and the FullHouse approval screen opens in your browser. See Cursor's [MCP guide](https://cursor.com/docs/context/mcp).

## Connect VS Code

In VS Code, use the guided setup: run **Chat: Open Customizations**, choose **MCP Servers**, then **Add Server**. Choose **HTTP** and enter the server URL. Follow the sign-in prompt when it appears.

Menu names may differ between versions. See VS Code's [MCP servers guide](https://code.visualstudio.com/docs/copilot/customization/mcp-servers).

:::note
VS Code's own configuration format uses `servers` as its top-level key rather than `mcpServers`. The **Others** tab mentions this too. Don't paste its snippet into a VS Code file without changing that. The guided setup avoids the problem.
:::

## Connect Codex

Codex is OpenAI's coding agent. Add FullHouse from your terminal, then sign in:

```bash
codex mcp add fullhouse --url https://app.meetfullhouse.com/mcp
codex mcp login fullhouse
```

To use an access token instead, add this to Codex's `config.toml` and set the named environment variable to your token:

```text
[mcp_servers.fullhouse]
url = "https://app.meetfullhouse.com/mcp"
bearer_token_env_var = "FULLHOUSE_TOKEN"
```

See OpenAI's [Codex MCP guide](https://learn.chatgpt.com/docs/extend/mcp?surface=cli).

## Connect Windsurf, Gemini CLI and others

For Windsurf, Gemini CLI and other tools, look in the settings or documentation for "MCP servers" and add a remote HTTP server using the server URL. Most will then offer to sign you in.

Field names vary between tools. Gemini CLI, for example, treats `url` as SSE and uses `httpUrl` for HTTP, or you can add a server with `gemini mcp add --transport http`. Its documentation also says it has been replaced by Antigravity CLI, so check which one you're using.

## Use an access token

If a tool asks for a header instead of signing you in, [create an access token](/mcp) and use this format, which is what the **Others** tab shows after its URL-only snippet. Formats vary between tools: some use a different name for `url`.

```json
{
  "mcpServers": {
"fullhouse": {
  "url": "https://app.meetfullhouse.com/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_TOKEN"
  }
}
  }
}
```

Replace `YOUR_TOKEN` with your token. The word `Bearer` and the space after it are part of the value. While the new token message is on screen, the snippet on the page already includes your token.

Keep your token out of anything you share. Don't commit it to a code repository or paste it into a chat. Where the tool supports it, keep the token in an environment variable. Cursor, for example, can read `${env:FULLHOUSE_TOKEN}` in its `headers`.

## Connect your own scripts

A developer can use an access token to call FullHouse from their own program, using any MCP client library. Point it at the server URL and send the token in the `Authorization` header as above. The token can't be sent any other way, such as in the web address.

Use **Read only** for reporting scripts, so a bug can't change anything.

## If a tool won't connect

| What you see | Likely cause | What to do |
| --- | --- | --- |
| Connection fails right after adding, with a mention of SSE or a "405" error | The tool is using SSE | Choose HTTP, or "streamable HTTP" |
| "401" or "Sign in to FullHouse to use this server." | The sign-in hasn't finished, or the token is wrong, expired or revoked | Finish the sign-in step. Check the token, including `Bearer ` at the start. Create a new one if needed. |
| "This origin may not call the FullHouse MCP server." | A tool running in your browser that FullHouse doesn't recognise | Use the tool's desktop version or a recognised tool such as Claude, ChatGPT, VS Code on the web or Cursor |
| "FullHouse can't verify this app's name…" on the approval screen | The app's address isn't one FullHouse recognises | Continue only if you started the connection a moment ago |
| The tool was working and now asks you to connect again | The app hasn't been used for 90 days, it was disconnected, or FullHouse closed it as a safety measure | Connect again. See [why a connection closes](/mcp/security). |
| The tools are listed but every action fails | Your plan doesn't include MCP or your workspace is suspended | Check the warning on **Workspace → MCP server** |

More messages are covered in [If something goes wrong](/mcp) and on [the approval screen](/mcp/connect-claude).

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