Assist With Music

AI

How Assist With Music's AI helps you make music — the reusable loops it runs, the signatures you teach it, and the research and public-domain texts it draws on.

Connect your AI agent

Assist With Music connects to any MCP client that speaks Streamable HTTP with OAuth. You paste the connector URL into your client, sign in, and approve the connection; Music keeps every read and handoff scoped to your workspace.

Connector URLhttps://assistwithmusic.com/mcp
  1. Step 1

    Add the connector

    Paste the URL into your AI client.

  2. Step 2

    Sign in

    Approve access to your own Music workspace.

  3. Step 3

    Start together

    Ask your AI to check Music context or your Queue.

Approving what a connected AI may do, seeing what it has done, and revoking it all happen in one place: AI connections →

Use https://assistwithmusic.com/mcp for new connections. https://thesongplanner.com/mcp remains available as a direct transport compatibility route for existing clients.

Reconnecting or refreshing tools does not delete your Music records.

Setting this up in your AI client

Music has not yet recorded a completed connection lifecycle for any named client. The clients named below are examples of each shape — not a claim that Music has run them.

Clients with a connector settings screen

You add Music from inside the client's own settings, in a browser or desktop app.

  1. Open the client's settings and find its connectors or MCP section.
  2. Add a custom connector and paste the connector URL.
  3. Continue, sign in to Assist With Music, and approve the scopes you want to grant.
  4. If the client caches its tool list, refresh it once the grant is in place.

Clients of this shape: Claude, ChatGPT, Cursor

Clients you configure from a terminal

You register the server with one command, then run the client's own sign-in step.

  1. Register the connector with your client's MCP add command.
  2. Leave the Authorization header off — omitting it is what triggers the OAuth sign-in.
  3. Run your client's authenticate or login step and approve the scopes.
  4. Refresh the tool list once the grant is in place.
<your CLI> mcp add --transport http assistwithmusic https://assistwithmusic.com/mcp

Clients of this shape: Claude Code, Codex

Loops

Reusable music skills — write, create, master, distribute, organize — the workflow the AI runs with you, end to end.

Open

Signatures

Capture exactly what makes a specific song sound the way it does, as a recipe your AI can reuse.

Open

Public-domain source texts

Hymns & scripture in the public domain the AI can set to music — browse them, or point your AI at them.

Open

Saved research

Your own studies of the artists behind the sound you are after — kept in your workspace, quietly there when you want them.

Open

The working agreement

How your AI works with Music

It reads before it writes

Your project direction is the creative brief. Hard avoid rules stay off-limits; styles marked use sparingly remain deliberate exceptions. Research, source facts, inferences, and drafts keep revision history and honest authorship.

It uses your real workspace

Finished lyrics and saved takes can appear in the normal Planner. Requests is the existing work desk. Queue is the shared four-state handoff view: Waiting for your AI, Needs you, Working, and Done.

It stops at your boundary

The MCP server never operates Suno itself. Your autonomy ceiling decides whether a connected desktop AI may prepare only or use an already signed-in session; it still stops before selection, download, publication, or distribution.

It can find the right method

Music Loops help it choose a repeatable workflow through songplanner_loops. Your private artist studies can guide projects without entering the public artist library.

Finding genres and Queue work

A connected AI can navigate the public genre encyclopedia from genres to families to direct subgenres, or run a concise ranked search, before it reads one exact rich entry. It never needs an unbounded encyclopedia dump. Private Queue rows also carry stable owner-scoped numbers such asQueue 42so you and your AI can name, retrieve, and continue the same handoff. Agents pass its queueNumber; the older opaque MUS-Q-…reference remains available only for compatible clients and links.

Album release preparation

A connected agent can assemble an owner-scoped cross-project album, bind each track to a selected version, and record portable mastering, quality, artwork, metadata, and distribution proof. This is preparation and recordkeeping only: there is no upload, submission, publishing, purchase, terms acceptance, or spend. External release actions remain with you.

If you ask your AI how to contact us

There is one answer, and it is not an email address. Assist With Music has no inbox and none is planned, so a connected AI is told never to offer, invent, or infer an email address for this site — no support@, no contact@, nothing built from the domain. Every request goes to the shared Assist With Life desk through /support, which shows its current status when you arrive. An assistant that hands you an address for Assist With Music has invented it.

Building on the API or want the full tool list and contract? See the agent guide →