Connect ChatGPT or Claude to Your Music Promo

Every other promo platform is a website you fill in by hand. Promo-Chats is the first one your own AI assistant can operate: a public API and an MCP server, so you describe the release in a chat and the campaign is waiting for you, built. You still decide when it goes out.

What this actually is

There are two ways in, and they lead to the same place. The API is a normal REST interface: create a key, call it from a script, a GPT Action, or anything else that speaks HTTP. MCP — the Model Context Protocol — is the standard an assistant uses to reach a tool on its own, so Claude sees Promo-Chats as something it can work in rather than a site it can only read about. One account, one set of rules, two doors.

The point is not novelty. Promo work is admin: the same release details typed into the same fields, the same list rebuilt for the same genre, the same follow-up a week later. That is precisely the part worth handing over — and the part you have never been able to hand over, because no promo platform would let anything but a browser in.

What an assistant can do, and what stays yours

A key carries scopes, and a scope it does not have is a door that is not there. Reading your campaigns, creating one, uploading assets and adding recipients are separate permissions you grant one by one.

• ✓Read your campaigns, contacts, lists and results — if you granted it.
• ✓Create a campaign from the release details and attach the audio, the artwork and the press note.
• ✓Build or extend a list, and add the recipients onto it.
• ✓Tell you what is still missing before a campaign can go out.
• ✓Read back who opened, who listened, who downloaded and who replied.

Sending is its own scope, off by default, and even switched on the send call is refused unless it carries an explicit confirmation. Two more things are not an assistant's to do: entering card details, and signing in to your Instagram or WhatsApp. A card needs its holder; a social login needs you. Everything before and after those steps is in the API.

There is no faster path in here. Anything queued through the API obeys the daily cap, the warm-up pace, the one-reminder-a-week rule, your sending window, the unsubscribe and bounce lists, and the guard that pauses a campaign by itself if addresses start bouncing. It is the same engine.

Connect Claude (MCP)

Create a key in the app under Setup → API, then add Promo-Chats as a remote MCP server:

{
  "mcpServers": {
    "promo-chats": {
      "type": "http",
      "url": "https://promo-chats.com/api/mcp",
      "headers": { "Authorization": "Bearer pc_live_YOUR_KEY" }
    }
  }
}

Then just talk to it: “Set up the promo for the new Occipital track, here is the WAV and the cover, send it to the techno list.” It creates the campaign, attaches the files, and stops to ask you before anything leaves.

Connect ChatGPT (Actions)

1. 1Create a key — in Setup → API. Copy it there and then: it is shown once and stored only as a hash.
2. 2Create a GPT — and add an Action to it.
3. 3Import the schema — from promo-chats.com/api/v1/openapi.json.
4. 4Authenticate — choose API Key, type Bearer, and paste the key.

From there your GPT works the account directly. The same schema works for any other tool that imports OpenAPI.

From an empty account to a promo

This is the whole path, in order. Everything here can be done by an assistant with the right scopes, apart from the one line in the middle.

GET   /api/v1/setup                  → what is still missing. Read this first.
PATCH /api/v1/settings               → sender name, reply address, sending hours
POST  /api/v1/lists                  → create a list
POST  /api/v1/contacts               → add the recipients onto it
POST  /api/v1/campaigns              → create the campaign
POST  /api/v1/campaigns/{id}/assets  → audio, artwork, press note
                       ── you pay for the campaign, in the app ──
POST  /api/v1/campaigns/{id}/send    → queue it, with confirm: true
GET   /api/v1/campaigns/{id}/stats   → what came back

The full reference, with the scope each call needs, lives on the developer page.

Why no other promo platform does this

FATdrop, Inflyte and Promoly are closed platforms: your list, your campaigns and your results live inside their site and come out as a screen. That model predates assistants, and it means the admin can never leave the browser tab. Promo-Chats was built the other way round — the app and the API are the same engine, so anything the app can do, a key can do.

There is a plainer reason too. An open API is only safe on top of sending rules that hold no matter who is calling. The caps, the reminder rule, the bounce guard and the confirmation on every send were already there for the app. The API just inherits them.

What it changes in practice

• ✓A release goes from folder to finished campaign in one conversation, at whatever hour you are working.
• ✓The follow-up question — who opened, who played it, who never answered — is asked in plain language, not built as a report.
• ✓The repetitive half of promo work stops being yours, and the judgement half still is.