Skip to main content
These are the tools, prompts, resources and skills the Soundcheck MCP server offers, and what you can ask your assistant to do with them. To connect a client first, start with Connect your AI to Soundcheck.

What the assistant can do

The generated MCP capability catalog lists the registered tools, resource URIs, prompts, and read/write counts for the source release. A connected deployment or cached connector can differ: list capabilities after connecting and check the build revision returned by initialize. Read tools are annotated read-only; consequential writes require explicit approval when the confirmation gate is enabled.

Member prompts

These are MCP prompts on the signed-in server (separate from the public three: quote_an_event, how_to_staff_a_live_event, plan_event_crew). Clients that support prompts can list them after connecting to https://mcp.soundchecklive.io/mcp. Consequential flows (text_my_crew, import/ingest commits, invites) still hit the confirmation gate on the underlying tools.

Toolsets

By default the member server lists its full tool catalog. To scope a connection to just the tools you need, pass a comma-separated toolsets query parameter on the connection URL (for example https://mcp.soundchecklive.io/mcp?toolsets=events,staffing) or an x-mcp-toolsets header with the same value. A small core set (your agenda, attention items, notifications, org lookup, docs search, the knowledge base, and the agent playbook) is always included regardless of what you pass. Omit the parameter, or pass all, to get everything. Toolsets only apply to the member server; the public tier’s tool list doesn’t change.

Renamed and merged tools

Some tools were merged into one tool with a parameter, or renamed. The old names are no longer listed by tools/list, but a tools/call with an old name still works: the server runs the new tool with the matching parameter set. Use the new names in new prompts and agents.

Available tools

Read tools

get_org_brief (a context primer on your organization: upcoming shows, everything waiting on you, its saved working notes and team), my_agenda, my_pending_actions.
One read tool per integration resource. QuickBooks: list_quickbooks_invoices, list_quickbooks_bills, list_quickbooks_payments, list_quickbooks_bill_payments, list_quickbooks_customers, list_quickbooks_vendors. HubSpot: list_hubspot_contacts, list_hubspot_companies, list_hubspot_deals. Flex: search_flex_contacts, list_flex_inventory, get_flex_quote. Google Drive or Dropbox: list_cloud_storage_files, read_cloud_storage_file. Slack: list_slack_gig_channels, list_slack_channel_messages. Each takes only its own filters. Read-only, for org admins and owners; an integration that is not connected answers NOT_CONNECTED. Reading Slack messages needs a Slack reconnect if your workspace was connected before this was added.
list_events (event_status=DELETED lists recently deleted gigs you can still restore), get_event (including the roster of crew working the show and, when the gig has a venue, its load-in and access details: the venue default, any per-gig override, and the value that applies), get_event_schedule, get_event_checklist, list_event_assignees (the org members assigned to manage it), get_event with view=cancellation_impact (who and what a cancellation would affect).
get_event_run_of_show, get_crew_requirements, list_outside_gear, list_event_links, list_show_contacts, get_staffing_plan (scope: "gig" for a gig’s labor call), list_venue_stages, list_space_holds, list_music_requests.
list_project_travel (a project’s or, with event_id, a gig’s flights, hotel stays, and passengers or guests), search_hotels.
list_event_chats (membership-scoped; SMS phone numbers are redacted for non-managers), list_event_chat_messages (stored citation records with immutable created_provider_timestamp; pass message_id for one message; members and gig managers only).
list_setlists (pass event_id for one gig’s setlists), list_songs (org song library), list_setlists, get_staffing_plan (scope: "templates" for team templates).
get_event_ledger (payables, receivables, income, expenses, and whether the show is ready to settle), list_ledger_accounts (income/expense accounts a ledger line posts to).
get_user_availability, list_availability_requests (pass request_id to read one; lists return 20 rows by default, up to 100 with limit, and page with offset), list_crew_offers (offers sent to you by default; scope=organization lists every shift on the org’s Staffing boards, DRAFT included, filtered by status, type, event_id, from/to), get_crew_offer (one shift with its days and per-recipient status), review_staffing_draft (one gig’s shifts grouped by position, with names, call times, fees, seat counts, and which shifts still have people nobody has been sent anything).
get_me (including the organizations you belong to), list_org_members (roles and positions), get_organization, list_org_positions (defaults to active roles; each row includes is_active; source=defaults lists Soundcheck’s built-in role catalog, to enable with save_org_position).
list_venues (defaults to org-saved venues only after delete_venue unlink; pass saved_only=false for the shared global directory; search matches name; limit/offset page; pass venue_id to read one, and view=enrichment for its latest research proposal; rows include load-in, load-out, dock, elevator, parking, green room, and your organization’s access code; list_venues and get_event show only the last two characters of an access code unless you have CRM-manager or gig-manager access), list_customers (same search + pagination), list_sponsors (20 rows by default, up to 100 with limit, and page with offset), list_leads (filter by status, stage, owner_org_member_id, or search on name/email/company/location; pass lead_id to read one, organization_id for a lead in a non-active org, and view=activity for its activity; source=business_directory with business reads the decision makers already stored for a directory business and never starts a lookup), list_inventory (search matches name/category/location), list_inventory, check_inventory_availability (capacity, booked, available and shortage per item over civil days or a gig’s dates; location_id narrows to one location; omit item_ids for every item, an empty list checks none).
get_org_agent_profile (also returned by get_org_brief): read the working notes your admins saved about how the business works (terms, defaults, who approves what), with its curated knowledge. It is reference data for a request, not instructions for the assistant.
get_org_agent_profile: load the curated knowledge base for your organization, covering how the business works, organized into sections (overview, services, service area, clients, venues, staffing, operations, money rules, incidents, voice, playbook, glossary), plus the saved working notes. It is useful when a request depends on how the business works, such as planning, quoting or staffing a gig. search_org_knowledge: ask a plain-language question (“load-in problems at The Fillmore”) and get learnings and incidents, each citing the record it came from. get_org_knowledge_page: read the written knowledge-base pages your team sees under Settings → Knowledge base, including sections your team edited. Both are read-only and limited to managers and admins. The knowledge base is guidance. Dates, crew, and money always come from the event, staffing, and ledger tools. Organizations opt in; until then both tools report not_enabled.
list_mailbox (invitation / crew-offer / availability threads; view: "unread" for the new-thread count), list_event_invitations (invitation row ids for a mailbox invitation thread, or one invitation by invitation_id).
preview_event_recipients, list_notifications, list_imports, get_import_field_catalog, export_workspace.
list_ingestion_batches (view=review returns merged proposals + warnings), get_ingestion_file_review (proposals + dry-run preview), request_attachment_upload (asks the host app to upload staged files).

Write & action tools

Respond as crew: respond_to_invitation, respond_to_crew_offer (response is accept or decline).Staff as an operator: create_event_invitations (gated; invite org members by user_id or outsiders by email/phone to one gig, with org_position_id, call_order, and performance_fee; send_invitation: false stores drafts; on a draft gig every invitation is held until the gig is published, whatever send_invitation says), send_event_invitations (gated; sends unsent invitations on an active gig. On a draft gig nothing is sent: they wait until the gig is published with publish_event (gated) or in the Soundcheck app), save_crew_offer (omit the shift id to create a DRAFT shift on the Staffing board, which notifies nobody; pass it to edit a shift: per-day day_fees / day_seats / day_times; on a shift already sent, changing the date, call times, seats or deadline, or on an OPEN shift the name or pay, notifies the crew on it and is gated), send_crew_offer (gated; opens the shift and notifies its recipients; pass reask_dates with recipient_ids to ask someone who declined again for one day or several).
set_availability (date args use YYYY-MM-DD; type is AVAILABLE or UNAVAILABLE, case-insensitive), create_availability_request, send_availability_request, respond_to_availability_request.
create_event (creates an active gig that crew can see unless you pass draft: true, which creates a draft like the Soundcheck apps do: hidden from crew, with invitations held until it is published with publish_event (gated) or in the app; adds the authenticated user as a member by default; pass member_ids to override; name is stored and returned as both name and title; start_time/end_time/event_date accept RFC3339 or unix epoch seconds as number or numeric string; omit timezone and the IANA zone is inferred from an RFC3339 start_time UTC offset such as -05:00 — unix seconds carry no offset, so pass timezone with them; end_date as YYYY-MM-DD, on or after event_date, makes a multi-day gig, which carries dates only, so start_time/end_time are refused with it), update_event (partial merge: an omitted field is unchanged; end_date: null makes the gig single-day; start_time: null / end_time: null clear call times; setting times on a multi-day gig is refused, and extending a timed single-day gig with end_date clears its times, copying them onto inheriting shift days and into an empty run of show; a blank string is rejected; gated only when it sets or clears event_date, end_date, start_time or end_time, or sets a non-empty location, because those send invited crew a schedule-change notification; title, notes and other metadata edits are not gated), duplicate_event (copies venue_id and adds you as a member; the copy is active unless you pass target_state: "DRAFT", a template source always becomes a draft, and copied invitations are unsent), archive_event (gated), unarchive_event (gated), add_event_member (gated; pass org_position_id from list_org_positions to staff a named role — each person joins the roster as INVITED and is added to the gig’s calendar invite), remove_event_member (gated; clears their pending invitations and calendar seat — payables and accepted offers are left for you to reconcile), link_venue_to_event, update_checklist_task (requires checklist_version from get_event_checklist), set_event_assignee (scoped manage rights on one gig; replaces the whole role set), remove_event_assignee.
update_event_run_of_show (gated; replaces the whole run of show, so send every section and item back. An existing section or item keeps its id. A new one has no id: give it a client_key of your own, unique in the call. An item joins an existing section with section_id, or a new section in the same call with section_client_key set to that section’s client_key. item_type is song, break, announcement or general, and blank means general. A section’s track is one of production, performance, vendors, hospitality, front_of_house, security, travel, ceremony_program or guests; custom track names are refused), create_event_schedule_items, upsert_event_schedule (gated; replaces the schedule), set_crew_requirements, add_outside_gear, save_event_link / remove_event_link, save_show_contact / remove_show_contact, save_gig_labor_call (the labor call header, or a department), create_hold, rank_hold, challenge_hold, withdraw_hold_challenge, release_hold and confirm_hold (all gated; hold a space and people, then act on the hold) (each save_* tool edits the row whose id you pass and adds a new one when you omit it), set_event_stages, unlink_event_venue, cancel_event (gated), delete_event (gated), restore_event (gated), save_event_as_template.
save_flight_passenger (pass passenger_id to edit, omit it to add), remove_flight_passenger (gated), save_hotel_guest (pass guest_id to edit, omit it to add), remove_hotel_guest (gated), create_hotel.
complete_event (mark a show complete, gated), settle_event (close the books, gated), reopen_event (undo a premature closeout, gated).
save_ledger_item (ledger_type INCOME, RECEIVABLE, EXPENSE, or PAYABLE; the account is resolved from list_ledger_accounts when the org has one of the matching type; INCOME and EXPENSE lines are created PAID because they record money already received or spent, while RECEIVABLE and PAYABLE lines start UNPAID; no money moves), save_ledger_item (UNPAID lines only), void_ledger_item (gated; UNPAID lines only; the line stops counting toward totals and settlement), record_ledger_payment (gated; records a cash, check, Zelle, Venmo, PayPal, wire, or other payment made outside Soundcheck, in full or in part, with an optional paid_on day; no money moves), reverse_ledger_payment (gated; undoes the latest manual payment on a line).
save_setlist (gated when you pass sets, because they replace the existing sets; when your organization keeps gig sets in Run of Show, a gig’s sets are written as song items in its run of show, the same way the Setlist view saves them), create_song, delete_setlist (gated), save_staffing_template (gated only when a members[] entry has delete: true, which removes that person from the template), apply_calllist_to_event (gated; all members: primaries insert INVITED, backups with is_backup or call_order !== 0 insert STANDBY; re-apply adds 0 new rows).
save_venue (shared record fields; "" clears text, null clears capacity/dressing_rooms/green_room; coordinates are set-only), update_venue_org_details (your org’s private org_notes / org_status / org_metadata and door or gate access_code; or pass event_id, field (load_in, load_out, dock, elevator, parking, green_room, or access_code) and value to override that field for one gig, or clear: true to fall back to the venue default; gated when it sets or clears an access code or a per-gig override), save_customer and save_sponsor (pass customer_id / sponsor_id to edit, omit it to create), save_lead (source is required when creating — WEBSITE, REFERRAL, INBOUND_EMAIL, PARTNER, REPEAT_CLIENT, INSTAGRAM, or OTHER; when editing, event_id / customer_id accept null to unlink), set_lead_owner (omit org_member_id to claim it yourself, pass null to unassign), mark_lead_lost, save_lead with reopen: true and a stage (brings a lost lead back), enrich_business (looks up the decision makers at a directory business and stores them on the shared directory record; list_leads source=business_directory reads them), convert_lead (gated; marks Won and creates a customer on an event), delete_lead (gated), save_inventory, assign_inventory, return_inventory, delete_inventory (gated), delete_venue (gated; unlinks the org overlay — default list_venues no longer returns it), delete_customer (gated).
create_import_from_paste (targets: EVENT, LEAD, INVENTORY, MEMBER), map_import, preview_import (dry run), commit_import (gated), preview_import_file (dry run), import_file (gated workspace clone). preview_import_file also returns a suggested vocabulary: each gig type, gig status and position the file uses, with counts and spelling variants collapsed, matched to the org’s own list or proposed as new. Pass accept_vocabulary (true or a list of suggestion keys) to import_file to create the new gig types, positions and Source status labels first. An org admin sets up labels, label groups and gig types with save_label (renaming or archiving is gated) and positions with save_org_position.
create_ingestion_batch, add_ingestion_file (pasted text, or filename + content_base64 for a binary file from a third-party MCP agent), commit_ingestion_file (gated), commit_ingestion_batch (gated). Analysis may not produce proposals; files can land attached-only when analysis never runs. Review what you have with the read tools, then commit what you choose.
update_org_settings (gated; owner/admin) changes only the settings you pass. timezone sets the org IANA timezone, which a gig with no timezone of its own uses. playbook replaces the working notes saved about how your business works; they are stored as reference data. tour_term_singular / tour_term_plural set what your organization calls a tour (Season, Residency, Run). Without one, the word follows your business type: Tour for bands and DJs, Series for venues, Project for everyone else. get_organization returns it as tour_term.
mark_mailbox_checked (clears the new-thread badge), send_reminder (gated; messages pending people; kind is invitation, crew_offer, or availability_request), reply_to_mailbox_thread (gated; write your own SMS or email to the pending, responded, or all people on an INVITATION, CREW_OFFER, or AVAILABILITY_REQUEST thread).
invite_org_member (gated; Clerk emails the invitee). Owners, admins, gig coordinators, and members given “Staffing on every gig” can call it. Default role is member, and gig coordinators and those members can invite as member only. Inviting an admin is owner-only. save_org_position (enable a catalog role by default_position_id, add a custom_name role, or rename, reorder, re-rate, or pass is_active: false to deactivate one) keeps the roster staffable.
send_message, broadcast_event_reminder: both gated; they preview and require an explicit confirmation before sending.

Resources

Browse and attach platform data as context using @ (in Claude Code) or + (in Cursor):

Skills

The member server also serves workflow skills: short playbooks that tell your assistant which tools to call, in what order, and where to stop for your approval. Soundcheck serves them through the MCP Skills extension (io.modelcontextprotocol/skills). A client that supports it lists them with skills/list, fetches one with skills/get, and reads each file as a skill://<name>/SKILL.md resource.

MCP Apps

In a client that supports the MCP Apps protocol, some tool calls open an interactive widget alongside the usual response instead of plain text:
  • Confirm card: shown for any confirmation-gated tool call. It lays out what the action will do, with Approve and Reject in place of typing a reply.
  • Plan review: opens on get_event_plan / review_event_plan. Shows a plan’s readiness and open questions, and lets you answer or dismiss them and mark it reviewed.
  • Staffing draft: opens on review_staffing_draft, get_crew_offer, and save_crew_offer. Shows the shift roster by position with recipient counts, with an action to send it.
Support depends on your client implementing the current MCP Apps protocol revision. A client that doesn’t falls back to the plain tool response.

In-browser context (WebMCP)

The web app also exposes a small WebMCP tool, get_current_context, directly on the page for a compatible browser AI extension. It reports which gig, plan, customer, venue, or other record you’re currently looking at so a WebMCP-aware assistant can pair it with the member MCP tools above to act on the record you’re viewing. When a record sits under a gig, such as an invoice, it also reports that gig. On a gig, it reports which tab you have open, such as Finances. On the Gigs list, it reports the gigs you’ve checked, so you can ask your assistant to act on that selection. It’s read-only and doesn’t expose data on its own.

Worked examples

Everything below is one message you can send your assistant. It picks the right tools; you approve anything consequential.
Runs get_org_brief to pull your upcoming shows plus every invitation, crew offer, and availability request waiting on you, and summarizes them. Follow up with “clear the ones I can” and it walks the accepts/declines with you.
Finds the event (list_events → get_event), then pulls the schedule, roster, setlist, and open checklist items (get_event_schedule, the get_event roster, list_setlists with event_id, get_event_checklist) into a single pre-show sheet.
Calls get_event_ledger to check outstanding items and lay out payables and receivables. If it’s ready, “settle it” runs settle_event, a gated action, so you confirm before the books close.
Drafts an availability request scoped to your drum positions (create_availability_request) and sends it to the crew (send_availability_request). Responses land in each member’s Mailbox and flow back into the calendar.
Uses duplicate_event to clone the positions and structure, update_event to set the new date, and link_venue_to_event (looking the venue up or creating it with list_venues / save_venue).
Reads my_pending_actions / list_crew_offers, then runs respond_to_invitation / respond_to_crew_offer with response: "accept" on the ones you name. Nothing is accepted without you saying so.
Reviews extracted proposals with list_ingestion_batches (view=review) when analysis produced them, shows you the schedule, crew, and money it found, and commits only what you approve with commit_ingestion_batch (a gated action). See AI file ingestion.
Lists inbound leads with list_leads (filter stage / status), reads one with list_leads lead_id, claims it with set_lead_owner, then converts with convert_lead (gated) onto the booked event. That creates the customer and marks the lead Won.
Finds the mics with list_inventory (search), then assign_inventory with event_id and quantity. return_inventory checks them back in after the show.
Drives create_import_from_paste → map_import → preview_import (a dry run you inspect) → commit_import (gated), so you see exactly what will land before anything is written.
Previews recipients with preview_event_recipients (use summary.broadcast_total as the expected count, since declined and standby members are not reminded), then sends via broadcast_event_reminder or a custom send_message. Both are gated, so it shows you the message and the list and waits for your yes.
Reads the saved working notes with get_org_agent_profile and replaces them with update_org_settings playbook (gated, owner/admin), so the note is on record the next time someone asks how your organization works.
Exports the source workspace with export_workspace, dry-runs its UEF document on the destination org you manage with preview_import_file, then commits with import_file (gated). Money, files, branding, and integration tokens stay out. See Export a workspace.
Checks the roster with list_org_positions (creating a missing role with save_org_position), lays down DRAFT shifts with apply_calllist_to_event or save_crew_offer, shows you the roster with review_staffing_draft / get_crew_offer, then send_crew_offer (gated) opens each shift and notifies the crew only after you approve. A 0-shift apply comes back with a hint naming the cause instead of a silent no-op.
save_ledger_item (RECEIVABLE; the income account resolves from list_ledger_accounts), then void_ledger_item (gated) on the duplicate. Both show on get_event_ledger; nothing is paid until you settle.
Lists the roster with list_org_members, confirms the email and role, then sends invite_org_member (gated) so Clerk emails them. Inviting a gig coordinator needs an owner or admin, and inviting an admin stays owner-only.

Connect your AI to Soundcheck

Endpoints, sign-in, security and troubleshooting.

MCP capability catalog

The generated list of tools, resources and prompts for each release.