We run a remote MCP server. Add it once as a custom connector and Claude can search our song catalog, read prices, hand you a payment link for a licence, or place an order for a song written to your brief — without leaving the chat. There is no sign-up and no API key: the connector only reaches public shop data.
https://music.cruscy.com/mcp as the remote MCP server URL. Leave the OAuth fields empty — this server is open.Connectors are available on Claude Pro, Max, Team and Enterprise plans; on Team and Enterprise an owner or admin adds them for the whole organisation. The exact menu wording changes now and then — look for “custom connector” / “add MCP server”.
Any MCP client that speaks Streamable HTTP works. In Claude Code:
claude mcp add --transport http cruscy-music https://music.cruscy.com/mcp
In a client that is configured with a JSON file:
{ "mcpServers": {
"cruscy-music": { "type": "http", "url": "https://music.cruscy.com/mcp" }
} }
Server passport for automatic discovery: /.well-known/mcp.json. Protocol versions supported: 2025-06-18, 2025-03-26, 2024-11-05. Transport: Streamable HTTP, POST only — the server never opens an SSE stream of its own, so a plain HTTP client is enough.
Search ready songs by words, language and length. Returns ids, titles, duration and a 30-second preview link.
Everything public about one track, plus the licence prices.
Current prices in USD and what each licence allows.
Makes a payment link for a licence on a track. Nothing is charged until you open the link and pay.
Orders a song written to your brief — your language, your voice, your name in the chorus. Returns a payment link.
Where an order stands: paid, queued, in production, ready — and the download link when it is.
The connector cannot read your account, cannot list other people's orders, and cannot take money. Payment always happens on a page you open yourself — Whop's checkout for cards, Apple Pay and Google Pay, or our own page for USDT. An order id is the only key to an order's status, and it is handed to you when the order is created.
Buying through the connector means the buyer accepts the Terms of Service, Privacy Policy and Content Policy — the tool descriptions say so, and the payment page shows them again before any money moves.
Reading a signed-in customer's own purchase history through the connector would need OAuth. It is not built: write to hello@cruscy.com if you need it and tell us what for.