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

# Connect heyBTW to Claude

> Add heyBTW as a custom connector with one URL and sign in. No API key, no config file.

heyBTW connects to Claude as a remote MCP server. You add one URL and sign in with your heyBTW account. Claude gets the heyBTW tools, prompts and guides for your workspace.

```text theme={null}
https://mcp.heybtw.com/mcp
```

This is the only URL you need. It works for every workspace: your sign-in decides which workspace Claude reads and writes.

## Before you start

* **A heyBTW account.** Sign up at [heybtw.com](https://heybtw.com) (Sign In, top right). Connecting from Claude does not create an account yet, so sign up first.
* **A Claude plan that supports custom connectors.** On a Team or Enterprise plan, an owner may need to add the connector for the organization first.

## Add the connector in Claude

**1. Open connector settings**

In Claude, open **Settings**, then **Connectors**, and choose **Add custom connector**.

**2. Paste the URL**

Name it `heyBTW` and paste `https://mcp.heybtw.com/mcp`. Leave any client ID and secret fields empty.

**3. Sign in**

Choose **Connect**. A heyBTW sign-in window opens. Sign in with the account that belongs to your workspace and approve access. The consent screen names read and write access.

**4. Turn it on in a chat**

In a new chat, open the tools menu and make sure heyBTW is enabled.

**5. Check it works**

Ask: "What can you see in heyBTW?" Claude calls [`get_workspace_overview`](https://heybtw.com/docs/tools/get-workspace-overview) and tells you your workspace, which integrations are connected and how many events it holds.

> [!TIP]
>
> The first call of a session can take a few seconds. See [Limits and errors](https://heybtw.com/docs/mcp/limits-and-errors.md).

## What access the connector has

| Access | What it covers |
| - | - |
| Read | Every `get_*`, `list_*` and `check_*` tool. Reads never change anything. |
| Write | Tools that create or change records in your heyBTW workspace: collabs, sign-ups, Lists, notes, tasks, observations. Each write tool says exactly what it writes, and most preview before they save. |
| Send | Only two actions send anything outside heyBTW: a Luma invite send ([`activate_list`](https://heybtw.com/docs/tools/activate-list)) and a collab co-host invitation ([`manage_collab_partners`](https://heybtw.com/docs/tools/manage-collab-partners)). Both preview first and wait for your explicit go-ahead. |

heyBTW never writes to your CRM, your mailbox or your event platform's guest list.

## Connect your other tools too

heyBTW is most useful next to the tools you already have in Claude.

* **Your CRM connector.** When Claude also has your CRM connected, it answers owner, deal and activity questions there and joins them to heyBTW on `email` and `company_domain`. See [Connect your CRM and event platform](https://heybtw.com/docs/playbooks/connect-crm-and-event-platform.md).
* **Your event platform.** Luma, Splash and Zuddl sync into heyBTW from the dashboard, not from Claude. Sign in at heybtw\.com, open **Integrations** for your workspace and add the platform's API key. [`get_workspace_overview`](https://heybtw.com/docs/tools/get-workspace-overview) gives the exact link as `connect_url`.

## Other MCP clients

Any MCP client that supports remote servers with OAuth sign-in can use the same URL. ChatGPT support is in progress and not yet verified end to end.

## Disconnect

Remove the connector from Claude's connector settings. Nothing in your heyBTW workspace changes.

## Next

> [card] [Your first session](https://heybtw.com/docs/mcp/first-session.md)

> [card] [How responses work](https://heybtw.com/docs/mcp/responses.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.