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

# Claude connector

> Connect Claude.ai or Claude Desktop to Soundcheck over MCP: directory listing when available, or a custom connector with the live member URL today.

Connect [Claude](https://claude.ai) or **Claude Desktop** to your Soundcheck account so you can brief shows, staff the engagement loop, and run everyday live-event work in plain language. Member tools use OAuth via Clerk. The assistant acts as you: it only sees what your login can see. 

Full capability list and confirmation gates: [Connect your AI to Soundcheck (MCP)](/integrations/mcp-server). 

## Connect Claude

### When listed in Claude's connectors directory

Soundcheck is **submitted for review** to Anthropic's Connectors Directory under the slug `soundcheck`. It is **not live in Browse connectors yet**. When it appears: 

1. Open [claude.ai](https://claude.ai) or Claude Desktop.
2. Go to **Customize** → **Connectors** → **Browse connectors**.
3. Search for **Soundcheck** and select it. 
4. Click **Connect** and finish the Clerk OAuth sign-in.
5. Confirm tools show under your connectors list.

No server URL paste is required once the directory listing is live.

### Today: add a custom connector

Until Browse connectors lists Soundcheck, use a custom connector with the live hosted URL: 

1. Open **Customize** → **Connectors** → **Add custom connector**.
2. Name it `Soundcheck` (member) or `Soundcheck (public)`. 
3. Paste the URL:
   * **Member (signed-in, OAuth):** `https://mcp.soundchecklive.io/mcp` 
   * **Public (anonymous discovery):** `https://mcp.soundchecklive.io/public/mcp` 
4. Save. For member, complete the browser OAuth sign-in when Claude challenges `401` + Protected Resource Metadata.
5. Start a chat and ask something like "What needs my attention this week?"

<Info>
  Official MCP Registry listing: `io.soundchecklive/soundcheck` **0.1.1-ts** (remote `streamable-http` → member URL). Prefer `mcp.soundchecklive.io` over any `api.soundchecklive.io` path.&#x20;
</Info>

## Member vs public

| Tier   | URL                                        | Auth          | What you get                                              |   |
| ------ | ------------------------------------------ | ------------- | --------------------------------------------------------- | - |
| Member | `https://mcp.soundchecklive.io/mcp`        | OAuth (Clerk) | Your gigs, crew, finances, CRM, gated writes              |   |
| Public | `https://mcp.soundchecklive.io/public/mcp` | None          | Org lookup, default positions, booking/sponsorship intake |   |

Public intake tools create real leads. Do not spam them.

## After you connect

* Consequential writes (messaging crew, committing imports, settling a show, deletes) are **confirmation-gated**: the first call does nothing and asks you to confirm.
* If you belong to multiple organizations, tools use your **active** org. Some first-connect flows leave `orgId` empty; pass `organization_id` on tools that accept it, or use a single-membership account for the first connect.
* Privacy: [soundchecklive.io/privacy](https://soundchecklive.io/privacy).&#x20;

## Related

<CardGroup cols={2}>
  <Card title="MCP overview" icon="robot" href="/integrations/mcp-server">
    Capabilities, tools, and security model.
  </Card>

  <Card title="Claude Code" icon="terminal" href="/integrations/mcp-claude-code">
    CLI connect with `claude mcp add`.
  </Card>

  <Card title="ChatGPT" icon="comments" href="/integrations/mcp-chatgpt">
    Plugin when listed; custom MCP today.
  </Card>

  <Card title="Cursor" icon="arrow-pointer" href="/integrations/mcp-cursor">
    Tools & MCP manual URL setup.
  </Card>
</CardGroup>