/ FOR LIMBO CUSTOMERS

Your catalogue, in your own words

Connect limbo/ to the assistant you already use, and work the way you talk. Ask what a record still needs, fix a credit, pull the numbers — against your own catalogue, in plain language.

Request your API key

/ ASK IT THINGS

The kind of question you already ask a person

What is still missing before I can ship the new record?
Which of my releases went out last month, and where to?
How did the single do in Mexico in its first two weeks?
Which albums are waiting on artwork?
Add the featured artist to track four.
Give me last quarter as a spreadsheet.

/ WHAT IT REACHES

Everything your account already holds

CATALOGUE

Albums, tracks, artists and labels. Search it, read it, fix what is wrong without leaving the conversation.

RELEASES

See what a record still needs, work through it, and send it for distribution when it is ready.

ANALYTICS

Plays, territories and platforms. Summaries, rankings and trends over any window you ask for.

DELIVERY

Which platforms a record reached, when it got there, and what each one still has pending.

/ CONNECT IT

Three steps, once

Get your API key

Keys are issued by the limbo/ team, one per account. Write to us and we will send yours — tell us which account it is for.

Request your API key

Take the endpoint

This is the address your client connects to. It speaks streamable HTTP.

ENDPOINT

https://mcp-test.limbomusic.com/mcp

Add it to your client

Find yours below. Each one wants the endpoint in a slightly different shape.

Claude web and desktop

Settings, then Connectors, then Add custom connector.

CONNECTOR URL

https://mcp-test.limbomusic.com/mcp

Claude opens the sign-in window itself once you add it.

ChatGPT

Settings, then Apps, then turn on Developer mode and add a custom connector. Web app only, on Plus, Pro, Business, Enterprise or Edu.

CONNECTOR URL

https://mcp-test.limbomusic.com/mcp

Enable it for your chats once the sign-in finishes.

Codex

Add the server to ~/.codex/config.toml.

~/.codex/config.toml

[mcp_servers.limbo]
url = "https://mcp-test.limbomusic.com/mcp"

Then run codex mcp login limbo to sign in.

VS Code

Create .vscode/mcp.json in your project.

.vscode/mcp.json

{
  "servers": {
    "limbo": {
      "type": "http",
      "url": "https://mcp-test.limbomusic.com/mcp"
    }
  }
}

Run MCP: List Servers from the command palette, start limbo, and authorize.

Cursor

Create .cursor/mcp.json in your project.

.cursor/mcp.json

{
  "mcpServers": {
    "limbo": {
      "url": "https://mcp-test.limbomusic.com/mcp"
    }
  }
}

Enable limbo from the Customize menu and sign in.

Antigravity

Add it to ~/.gemini/config/mcp_config.json. Antigravity needs the serverUrl field — the older url and httpUrl fields are not supported there.

~/.gemini/config/mcp_config.json

{
  "mcpServers": {
    "limbo": {
      "serverUrl": "https://mcp-test.limbomusic.com/mcp"
    }
  }
}

Antigravity handles the sign-in on its own.

Zed, Windsurf and everything else

Clients that cannot open a streamable HTTP connection yet reach it through the mcp-remote proxy.

SERVER COMMAND

npx -y mcp-remote https://mcp-test.limbomusic.com/mcp

The proxy opens the same browser sign-in on first run.

SIGNING IN

The first time you connect, your client opens a browser window. Paste your API key there once and you are done — your client remembers it and refreshes on its own.

Nothing else needs configuring. No tokens in config files, no secrets to keep in sync.