Connect your AI to Soundcheck (MCP)

​

What you can do with it

​

Connect from your assistant

​

Public discovery

• quote_event: event description (plus optional date, location, structured requirements) → grounded synthetic estimate range, breakdown, assumptions, confidence, missing_information, evidence, and a stateless quote_id; pass quote_id plus overrides to refine. Optional use_ai_grounding uses the same analysis service as analyze_event_to_uef to fill gaps in the extracted event facts only (prices are never model-generated).
• list_quote_packages: browse the pricing catalog behind quote_event (event profiles, package tiers, add-ons, market indexes, rules, catalog version) — the evidence a quote cites
• get_public_org: org lookup on the public storefront
• list_positions: global default position catalog (not the looked-up org’s roles; no org id)
• normalize_positions: map free-text crew role strings onto the global position catalog (deterministic; not AI-gated)
• analyze_event_to_uef: turn pasted event text into a UEF draft plus missing fields (analyze only; always listed; AI call fails clearly when gateway is unavailable)
• get_uef_schema: versioned UEF JSON Schema textbook (schema_version 1.0, minimal + festival examples, docs URL; no AI)
• validate_uef: validate a UEF draft locally (valid / errors / missing_required; no AI, no invented fixes; 256 KiB string cap)
• search_places / get_place: seeded public industry venue + hotel catalog (not a complete world database; unknown names return empty/suggestions, never invented addresses)
• search_inventory / normalize_inventory: public live-event gear taxonomy (stable ids + aliases; not org stock)
• lookup_market_pricing: market price ranges per service category with the evidence behind them (published rates plus Soundcheck actuals released only as ≥3-organization aggregates; returns coverage: "none" and no numbers when evidence is missing — no price is ever invented)
• request_booking: booking intake (creates a lead)
• request_sponsorship: sponsorship intake (creates a lead)

​

Hosting status

​

Connect your client

​

Public (anonymous)

claude mcp add --transport http sc-public https://mcp.soundchecklive.io/public/mcp

{
  "mcpServers": {
    "sc-public": {
      "type": "http",
      "url": "https://mcp.soundchecklive.io/public/mcp"
    }
  }
}

{
  "mcpServers": {
    "sc-public": {
      "type": "http",
      "url": "https://mcp.soundchecklive.io/public/mcp"
    }
  }
}

​

Member (signed-in, OAuth)

• OAuth via RFC 9728 Protected Resource Metadata
• Clerk authorization server: https://clerk.soundchecklive.io
• Authorization code + PKCE
• No pasted session JWT for first-run connect
• Do not invent a static client_id. Clerk may advertise Dynamic Client Registration metadata; do not assume naive clients can complete DCR for member connect today.

claude mcp add --transport http sc https://mcp.soundchecklive.io/mcp

{
  "mcpServers": {
    "sc": {
      "type": "http",
      "url": "https://mcp.soundchecklive.io/mcp"
    }
  }
}

​

How sign-in works

1. Hit https://mcp.soundchecklive.io/mcp and receive a 401 with a WWW-Authenticate challenge that includes resource_metadata (RFC 9728) and Clerk’s as_uri.
2. Fetch /.well-known/oauth-protected-resource and read authorization_servers (lists https://clerk.soundchecklive.io).
3. Complete the OAuth browser sign-in your client supports. Do not paste a static client_id. Do not assume Dynamic Client Registration works for every naive client.
4. Cache the access token for later calls.

​

What the assistant can do

​

Member prompts

​

Available tools

​

Read tools

​

Write & action tools

​

Resources

​

What MCP cannot do yet

• Paying a ledger line or funding a payout: create_ledger_item / update_ledger_item / void_ledger_item keep the books and record_ledger_payment / reverse_ledger_payment record payments made outside Soundcheck, but paying an individual line through Soundcheck (Cleo / card) stays in the GUI; settle_event (gated) closes the show.
• Seat and billing changes: MCP cannot change subscriptions or billing. Member-management actions remain subject to the signed-in account’s role; check the connected server’s tools before using them.
• Public MCP workspace clone: no export_workspace or import_uef on the public endpoint. Member MCP can clone; full rosters stay off public MCP. See Export a workspace.

​

Worked examples

​

Security model

• Each member request carries your Soundcheck (Clerk) token. The server validates it on every call and forwards the validated token to the Soundcheck API.
• The server has no privileged credentials beyond your own account. It acts as you, never as an admin, and can’t reach data your login can’t.
• Mutations are flagged with MCP annotations (readOnlyHint, destructiveHint, idempotentHint) so clients can prompt for confirmation.
• Confirmation gate. Consequential tools (send_message, broadcast_event_reminder, remind_invitation, remind_crew_offer, remind_availability_request, invite_org_member, commit_import, import_uef, commit_ingestion_file, commit_ingestion_batch, complete_event, settle_event, reopen_event, archive_event, unarchive_event, set_org_playbook, set_org_timezone, delete_venue, delete_customer, delete_song, delete_setlist, delete_lead, delete_inventory, convert_lead, create_event_invitations, send_event_invitations, send_crew_offer, remove_event_member, void_ledger_item, record_ledger_payment, reverse_ledger_payment, and reply_to_mailbox_thread) go further: when the gate is enabled they perform nothing on first call and return {status:"confirmation_required", confirmation_token, summary, expires_in_seconds}. The action runs only when the same call is repeated with that token, so a single stray tool call can never message your crew, commit a write, archive a gig, or settle a show. For ingestion commits the token also binds the exact proposals you reviewed, so a re-merge automatically re-gates the commit. Soundcheck’s own assistant turns this into a plain “reply YES to send” step, and only the original requester can approve.
• TLS is required (HTTPS only). Production ingress redirects HTTP to HTTPS. There is no HSTS claim in this surface.

​

Troubleshooting

​

For agents

• Product: https://soundchecklive.io
• Public docs (this page): https://docs.soundchecklive.io/integrations/mcp-server
• Agent discoverability playbook: https://docs.soundchecklive.io/integrations/mcp-discovery
• Official AI-info: https://docs.soundchecklive.io/ai-info
• Privacy policy: https://soundchecklive.io/privacy
• Public MCP: https://mcp.soundchecklive.io/public/mcp
• Member MCP: https://mcp.soundchecklive.io/mcp (OAuth via Clerk)
• Registry: io.soundchecklive/live-event-quotes 0.1.0 (public) and io.soundchecklive/soundcheck 0.1.1-ts (member)

​

Related