Suno MCP Beta: Make Songs Inside Claude and ChatGPT, and the Download Rule to Know

Source: Author

Making a song with AI help has usually meant two windows. Lyrics in a chat assistant, then copy, paste, style, generate and listen in Suno, then back to the chat to fix the bridge. Repeat.

That loop got shorter on October 28, when Suno listed a beta of its own MCP server in its release notes. It links your Suno account to Claude, ChatGPT, Gemini, Claude Code and Cursor, so the assistant you already write with can make the track too. The early-access button is the hurdle people notice first, but the rules that matter more sit in your assistant's plan and in Suno's terms.

What you can do from the chat

• Describe a song in plain words. The assistant writes lyrics and a style prompt, and Suno generates it.
• Start from your own audio, such as a voice memo or a short clip, and turn it into a full song.
• Remix your library with covers, mashups and extensions.
• Use your own voice if you have set up a Suno Voice. Voices arrived with Suno v5.5 in March and need a Pro or Premier plan plus a short live verification.

Whatever you make is saved to your Suno library, the same as work done on suno.com. There is no API key either: a one-time Suno sign-in and approval is all it takes. Generations draw on the same credits as the website, and you can ask the assistant for your remaining balance. Suno's help center says the beta works on every plan, Free included.

The bigger change is context. MCP, the open standard Anthropic introduced in November 2024, lets an assistant call outside tools. The request now comes from a chat that already knows your outline and lyric draft, so you can ask for changes the way you would brief a producer.

A chat request passes through the Suno connector into your library, and only the winning take gets downloaded

Connecting it

Every assistant uses the same address, https://api.suno.com/mcp; only the menu changes. In Claude Code, a new server works only in the current project by default. Add --scope user to use Suno everywhere, or --scope project to write a shareable .mcp.json file.

Three gates before a song is usable

1. Early access. The main button on Suno's MCP page is a "Get early access" sign-up. Join it before configuring anything.
2. Your assistant's plan. Suno is added as a custom connector, and each assistant decides who can do that. On Claude, free accounts can add one custom connector. On Team and Enterprise, an owner adds it for the organization and each member links their own Suno account.
3. Suno's download rule. Under Suno's updated terms, in force since September 3, 2026, commercial use is allowed only for songs you downloaded through an approved channel, and each plan caps how many downloads you get.

How many songs each Suno plan can download, and what you can do with them

The third gate is easy to trip over in a chat, where asking for three more versions feels free. Each one is a generation, and generating easily outpaces your plan's download allowance. Explore freely, then download only the winner.

Worth knowing before you publish

• Songs may carry a fingerprint, watermark or metadata that identifies the plan behind them, and the terms forbid stripping it to disguise a song's source.
• Paid plans hand you Suno's rights in the output, but Suno makes no promise that any song is protected by copyright.
• Songs made on the Free plan don't gain commercial rights when you upgrade later, although Suno says it may offer them in some cases.
• Copy the address only from Suno's own page, and be careful with "Allow always", since every generation spends credits.

Read the full Suno MCP guide on Medium →

Where to add the connector in each assistant, five workflows to try first, and how to switch it off safely.