Skip to main content
Use Soundcheck’s hosted MCP endpoints to connect a supported external assistant. Choose the endpoint for the data you need, then follow your client’s setup guide.

​
Which endpoint should I use?

Start with quote_event when an agent needs live-event pricing: it returns a labeled synthetic estimate grounded in Soundcheck’s public pricing catalog, never a model-invented number. The public endpoint does not expose private rosters or provide public gig search. Booking and sponsorship intake create real inquiries; submit them only when you intend to contact that organization. Analysis tools can return an unavailable error when the analysis service is unavailable.
External MCP access is separate from CheckAI beta, Chat beta, and E-sign beta. Those features are Private Preview, available only to the existing beta tester group. Signing up, paying, upgrading, contacting support, viewing a public demo, or connecting MCP does not grant preview access.

​
Connect your assistant

Claude

Connect Claude with the hosted MCP URL.

Claude Code

Configure the hosted server in Claude Code.

ChatGPT

Review custom connector setup and account requirements.

Cursor

Add Soundcheck under Tools & MCP.
Use the production URLs above. A client must support the server’s authentication flow for member access; never invent a client ID to complete setup. See MCP authentication and capabilities.

​
Registry and directory status

Soundcheck has two official MCP Registry listings: io.soundchecklive/live-event-quotes, version 0.1.0, pointing to the anonymous public endpoint, and io.soundchecklive/soundcheck, version 0.1.1-ts, pointing to the hosted member endpoint. Registry listing versions and server runtime versions are separate. The current documented rollout has the Claude Connectors Directory and ChatGPT directory submissions awaiting review, with no Cursor Marketplace plugin published. Use the custom connection guides above while a listing is unavailable. A public listing or demo does not enroll anyone in Private Preview.

​
Learn the workflows

​
Verify the capabilities you connected to

The generated capability catalog records the SDK source release. Use the connected server’s tools/list, resources/list, resources/templates/list, and prompts/list responses for deployed capabilities. initialize.result.serverInfo.version carries the deployed Git revision after + when the host supplies build provenance. Registry versions and cached connector tool counts do not identify a deployment.