Connecting Claude to your Locker
Let Claude and other AI apps work with your catalogue, safely and on your terms.
What this is
You can connect the AI you already use, like Claude, straight to your Locker. Once connected, it can search your catalogue, check credits and splits, look at playlists and projects, read your history, and (with your approval) make changes, all from inside your AI app.
It works with any app that speaks the Model Context Protocol, including Claude on the web, Claude Desktop, and Cursor.
Connecting AI apps is included on every paid plan at no extra cost. The free plan keeps full in-app Kii; connecting outside apps is a paid feature.
Connect Claude in three steps
- In Claude, open Settings, then Connectors, then Add custom connector.
- Paste your Locker server address. You will find it in Locker under Profile, then Connections.
- Claude sends you to Locker to approve the connection. Review what it is asking for, click Approve, and you are done.
That is it. Claude stays connected until you disconnect it. You can manage every connection from Profile, then Connections.
Staying in control
You are always in charge of what a connected app can do:
- Every change asks first. Before an app edits anything, it shows you exactly what it plans to do and waits for your go-ahead.
- Everything is on the record. Every action a connected app takes appears in your History, labelled with the app that did it.
- Disconnect any time. One click in Profile, then Connections, and the app loses access straight away. Nothing in your catalogue is deleted.
- Your limits still apply. A connected app cannot push you past your plan’s storage or analysis limits.
A connected app never sees your password or payment details, and it cannot permanently delete your tracks.
Personal tokens for developers
If you use a tool that does not have a built-in connect button, or you are writing your own script, you can create a personal token instead. Turn on Developer settings at the bottom of the Connections page, create a token, and paste it into your tool alongside the server address.
A token is shown once when you create it. Store it somewhere safe, and revoke any token you stop using.