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

# Developers

> Build on Soundcheck. Connect an AI assistant or agent over MCP, and move data in and out with the Soundcheck import file.

This tab is for people who connect software to Soundcheck: AI assistants, agents, scripts and other systems. If you run gigs day to day, start with [Gigs](https://docs.soundchecklive.io/features/gigs/overview.md) instead.

There are two ways in today.

> [card] [MCP server](https://docs.soundchecklive.io/integrations/mcp-server.md)
>
> Point Claude, ChatGPT, Cursor or any MCP client at your Soundcheck account. Your assistant reads gigs, crew and finances and does everyday work with the same permissions you have.

> [card] [Import file](https://docs.soundchecklive.io/features/imports/universal-event-format.md)
>
> One JSON file that moves a workspace's data into or out of Soundcheck. Use it to migrate from another tool or to feed Soundcheck from your own systems.

## AI and agents

To connect now, add one of these URLs to your MCP client:

| Endpoint | URL | Sign-in |
| - | - | - |
| Member | `https://mcp.soundchecklive.io/mcp` | Your Soundcheck account (OAuth) |
| Public (Soundcheck Event Directory) | `https://mcp.soundchecklive.io/public/mcp` | None |

In Claude Code, for example:

```bash theme={null}
claude mcp add --transport http soundcheck https://mcp.soundchecklive.io/mcp
```

* [Connect your AI to Soundcheck](https://docs.soundchecklive.io/integrations/mcp-server.md) explains the public and member endpoints and how sign-in works.
* [MCP tools reference](https://docs.soundchecklive.io/integrations/mcp-server/tools.md) describes the tools by area, with examples you can send your assistant. The [generated catalog](https://docs.soundchecklive.io/integrations/mcp-catalog.md) lists every tool, prompt and resource.
* Setup guides for [Claude](https://docs.soundchecklive.io/integrations/mcp-claude.md), [ChatGPT](https://docs.soundchecklive.io/integrations/mcp-chatgpt.md), [Cursor](https://docs.soundchecklive.io/integrations/mcp-cursor.md) and [Claude Code](https://docs.soundchecklive.io/integrations/mcp-claude-code.md).
* [Discovery and connection options](https://docs.soundchecklive.io/integrations/mcp-discovery.md) covers registry and directory listings.
* To search these docs from your assistant, add the docs MCP server: `https://docs.soundchecklive.io/mcp`.

## Data formats

* [The Soundcheck import file](https://docs.soundchecklive.io/features/imports/universal-event-format.md) describes the shape of the file.
* [Import file fields](https://docs.soundchecklive.io/features/imports/import-format-reference.md) lists every field, with an example for each kind of record.
* [Stability and versioning](https://docs.soundchecklive.io/features/imports/import-format-stability.md) says what we promise not to break and how you hear about changes.

## REST API

There is no public REST API reference yet. Pages that mention an `/api/v1/...` path describe what the Soundcheck apps call, not a supported public interface. The MCP server covers most of what an integration needs. API access for your own systems is an Enterprise feature; to ask for it, email [info@soundchecklive.io](mailto:info@soundchecklive.io) with what you want to build.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.