Use Labelcamp from your AI assistant
Ask your AI assistant about your catalogue, upcoming releases or streaming figures, and it finds the answer in Labelcamp. It uses your account and your permissions.
What's coming out in the next two weeks? And how did last Friday's single start?
3 releases in the next two weeks:
| Release | Date | Status |
|---|---|---|
| Low Light (single) | 2026-10-02 | Active |
| Riverstone (album) | 2026-10-09 | Active |
| Drift (single) | 2026-10-09 | Active |
Last Friday's single, Paper Moons, had 42,000 streams in its first three days and was added to two editorial playlists.
Nice. Where is it growing fastest?
In France (+65% from Saturday to Sunday), then Belgium and Canada. Most of the growth comes from playlists.
How it works
Every action goes through Labelcamp and passes the same checks and validations as in the app.
Before modifying anything, the assistant shows what it will change and waits for your confirmation.
The assistant has the same access as your Labelcamp account.
Sign in with your Labelcamp credentials. No separate account is needed.
Supported assistants
The connector uses MCP, an open standard for connecting AI assistants to other applications. Once installed, it's available in every conversation.
Getting started
-
Get access. The connector is enabled per account. Ask your administrator to turn it on for yours.
-
Add the connector to your assistant and sign in with your Labelcamp credentials. This takes a couple of minutes.
-
Ask your first question:
What can I do with Labelcamp?
The assistant should list what your account can do. If it doesn't, see Troubleshooting.
Access & security
The assistant has the same access as your Labelcamp account, never more, and never sees your password. Details in Access & security.
Limits
A few limits protect Labelcamp and your catalogue. You rarely hit them in a normal conversation.
- Number of requests: the assistant can send only a certain number of requests in a short period. The limit applies to your account, and also to your group as a whole: every user of the group shares it, so a busy colleague can use it up for everyone. When the limit is reached, the assistant stops, is told how long to wait, and tries again after that delay. If you hit it often, split large analyses into several smaller questions.
- Size of a change: each bulk change applies to a limited number of items, depending on the operation. A plan that reaches the limit says so: split the request, for instance label by label or year by year.
- Duration of a request: a very broad question, such as the whole catalogue over several years, can time out. Narrow the period or the scope, or ask for a CSV export instead.