> ## 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.

# ChatGPT plugin

> Connect ChatGPT or Codex to Soundcheck over MCP: OpenAI directory plugin when available, or paste the live member URL as a custom MCP today.

Connect **ChatGPT** (and Codex where MCP is supported) 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.&#x20;

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

## Connect ChatGPT

### When listed in the OpenAI directory

Soundcheck's ChatGPT / Codex plugin is **submitted for review and not live in the OpenAI directory yet**. When it appears:&#x20;

1. Open [chatgpt.com](https://chatgpt.com) (or the ChatGPT app).
2. Open the plugins / apps directory and search for **Soundcheck**.&#x20;
3. Click **Install** / **Connect** and finish the Clerk OAuth sign-in.
4. In a chat, `@`-mention Soundcheck (or enable it for the conversation) and ask about your shows.&#x20;

### Today: custom MCP URL

Until the directory listing is live, add a custom / remote MCP server with the hosted URL your ChatGPT or Codex client supports:

| Tier                 | URL                                        | Auth            |   |
| -------------------- | ------------------------------------------ | --------------- | - |
| Member (recommended) | `https://mcp.soundchecklive.io/mcp`        | OAuth via Clerk |   |
| Public (anonymous)   | `https://mcp.soundchecklive.io/public/mcp` | None            |   |

1. In ChatGPT / Codex MCP settings, add a remote **Streamable HTTP** server.
2. Paste the member URL for signed-in tools, or the public URL for anonymous discovery.
3. Complete the browser OAuth flow for member (expect `401` until sign-in finishes).
4. Ask something like "Give me a one-page brief for Friday's show."

<Info>
  Official MCP Registry listing: `io.soundchecklive/soundcheck` **0.1.1-ts**. Prefer `mcp.soundchecklive.io` over any `api.soundchecklive.io` path. There is **no** Cursor Marketplace plugin yet either; Cursor uses the same URLs manually.&#x20;
</Info>

## Member vs public

* **Member** — your events, crew, availability, setlists, finances, CRM, and gated write actions.
* **Public** — org lookup, default position catalog, booking and sponsorship intake (creates real leads; do not spam).

## After you connect

* Consequential writes are **confirmation-gated**: the first call returns a confirm step and writes nothing until you approve.
* Multi-org accounts: tools operate in your **active** organization. If first connect leaves `orgId` empty, pass `organization_id` on tools that accept it.
* 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" icon="message" href="/integrations/mcp-claude">
    Claude.ai / Desktop custom connector today.
  </Card>

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

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