Suno MCP setup

Check two separate kinds of access

Suno’s 28 October announcement says MCP is available across Suno plans, while still inviting users to early access. Treat that as a beta rollout: a paid Suno subscription alone is not proof that your account has been admitted. Use the official signup if access is unavailable. Suno MCP beta announcement.

Your AI client has its own account and workspace rules. If the custom-connector control is missing, resolve that client restriction before troubleshooting Suno. Never paste a password, browser cookie or session token into chat to work around it.

Claude chat or Claude Desktop

Claude’s custom-connector flow asks for a name, remote URL and authentication settings. Add the endpoint below and complete Suno sign-in; inspect the account on the approval screen. Claude currently documents one custom connector on Free, with separate workspace controls on team plans. Claude remote-connector setup.

Suno’s official route uses account sign-in rather than a Suno API key. Suno authentication.

Claude is rolling out a unified Plugins page that replaces the Customize menu. If you see the newer interface, find the connection under Plugins and use its connector controls; menu wording can differ during rollout. Claude’s interface transition.

https://api.suno.com/mcp

Claude Code

Register the remote HTTP server, then open /mcp inside Claude Code to authenticate:

claude mcp add --transport http suno https://api.suno.com/mcp

This follows Suno’s command. Registration and authentication are separate: inspect the connection status after sign-in. Scope matters; a server added for one project need not be available in another. Claude Code’s MCP reference.

Cursor

Add a user MCP server from Cursor’s Customize settings, or merge this entry into the existing mcpServers object. Keep your other entries intact:

{
  "mcpServers": {
    "suno": {
      "url": "https://api.suno.com/mcp"
    }
  }
}

Cursor supports remote HTTP with OAuth. Its documented user-wide configuration is ~/.cursor/mcp.json; project configuration has a narrower scope. Finish authorization and inspect the discovered tools before use. Cursor MCP documentation.

ChatGPT

Suno describes Plugins → Add → Add custom MCP server. OpenAI’s current help page lists custom MCP access for Business and Enterprise/Edu on the web, with workspace permissions. Use that route only if your account offers it; do not assume an individual subscription includes it. Enter the Suno endpoint, configure the requested authentication, create the plugin, then connect your account. Current ChatGPT custom MCP requirements.

Attach the available connection to the conversation. This is native MCP, not a Custom GPT Action with an OpenAPI schema. Using connected apps in ChatGPT.

Gemini and other clients

Suno lists Gemini among supported clients. Verify that your particular app, plan and workspace expose a remote connector with the required sign-in flow. A product name alone is not a connection check. Suno’s client options.

First, ask for information only

Use this original prompt after connecting. It avoids naming tools that may differ across the beta rollout:

Use the connected Suno tools only to inspect my account and remaining credits.
Do not generate, remix, extend, upload or modify music.
Show the available tool names and which account is connected, if the tools expose it.
If an account or balance field is unavailable, say so instead of guessing.
Stop after this check.

Suno says MCP songs consume your existing plan’s credits and are saved in your Suno library. Its FAQ also describes asking the assistant for the remaining balance. Credits and library behavior.

Read the proposed tool request. A prompt is a request to the assistant, not an account-level spending cap. If the balance cannot be retrieved, inspect it directly in Suno before proceeding.

Then define one bounded music request

Prepare a short brief: intended use, instrumental or vocals, style, desired structure, and material you have permission to supply. For a first check, use a fresh text idea without an upload. Ask the assistant to show the proposed operation and the expected charge if available, and to wait for approval. Confirm the current account’s charge for the chosen operation; do not assume a fixed price per song.

Avoid “keep making variations until it sounds good.” Ask for one generation operation, no automatic retries and no follow-up remix. One operation need not equal one returned track; record the actual results.

Keep a result record

Copy this locally and fill it with the actual response, not an expected outcome:

Suno account checked:
Client and connector:
Request submitted at:
Operation or job reference (if returned):
Credits before:
Credits after:
Returned song links:
Same-account library check:
Playback and content check:
Unresolved error or missing result:

Open each returned song in the same account’s library and play it. Check the intended voice/instrumental choice, usable duration and unwanted content. A generated title or the assistant saying “done” is insufficient. If several songs were returned, inspect each.

Before publishing music, review the terms that apply to your account and creation. Connecting through MCP does not establish commercial-use rights.

No connector setting: check the client plan, workspace permission and specific app. Use a route from Suno’s setup page; do not install a similarly named third-party package as a substitute for the official connection.

Sign-in completed, but access is refused: confirm the Suno account and beta status first. Save the exact error with the client/version and time. Repeatedly adding the URL will not grant early access.

Tools are missing: verify that the server is enabled and attached to this conversation. In Claude Code, /mcp distinguishes configured servers from their connection status; in Cursor, inspect the enabled tools for the entry. Claude Code status checks · Cursor tool controls.

Balance looks wrong: compare the account in the browser authorization with the account whose library and credits you expected. Keep the original session until you know which account performed the operation.

Generation times out or the chat disconnects: inspect the existing library and any returned job reference before resubmitting. Record the credit change. A client timeout alone does not tell you whether Suno accepted the request; generating again could duplicate work.

No song is visible: check the same account and the returned links, then preserve the request reference and error for Suno support. Without a library result or provider receipt, mark the outcome unresolved.

Remove or disconnect Suno in the client where you added it. For ChatGPT, manage the connected account from plugin settings; changing conversations is not the same as disconnecting the account. ChatGPT connection management.

Current Claude Code documents logging out before removing a remote server:

claude mcp logout suno
claude mcp remove suno

Logout requests provider-side revocation where supported; removing the server deletes local registration and tokens but does not itself revoke them at the provider. Check your installed client’s help if these commands differ. Claude Code removal and OAuth behavior.

For Cursor, remove or disable Suno in the relevant MCP configuration and use any available sign-out control. Verify that a new conversation cannot use the removed connection.

The public Suno MCP pages reviewed here do not specify a universal account-side revocation screen or guarantee token invalidation for every client. If provider-side revocation is needed and the client cannot confirm it, contact Suno support. Hiding a tool or deleting a chat is not proof that all authorization has ended.