Suno has released an official MCP server, in beta, that lets people generate and edit music from inside AI apps that support the Model Context Protocol. The hosts it lists are ChatGPT, Claude, Gemini, Claude Code and Cursor. Suno presents it as music-making inside the assistant a person already uses. Access currently runs through an early-access signup form, and the launch was covered on 28 October 2026.
Setup comes down to adding the endpoint https://api.suno.com/mcp as a custom connector or custom MCP server. There is no API key: the user signs in to Suno and approves the connection. In Claude Code the install is a single command, claude mcp add --transport http suno followed by that URL; in Cursor the URL goes into the mcp.json file, and in Gemini a user mentions @Suno in a chat once the connector is added. In ChatGPT and Claude, custom connectors need certain paid plans.
Once connected, a user can ask the assistant to make a song from a plain-text idea, turn a voice memo into a track, or remix, cover, mash up and extend songs already in their library. A saved Suno Voice can be applied too, and the assistant can report how many credits are left. Songs spend credits on the user's current Suno plan and are saved to their Suno library. Suno's own pitch is that the assistant can reuse what was already discussed in the chat, such as lyrics or a video plan, so nobody has to explain it twice.
The release follows Suno's Speech Beta, which makes voice and music in a single track, and the v6 release with plain-language section editing and mashups. Unofficial Suno MCP servers existed before, often built on browser automation or third-party API resellers, which meant driving Suno through a headless browser or paying an outside service for access. The reporting notes that an official endpoint removes the Playwright and headless-browser workarounds those relied on.
Suno's share preview image for its MCP page
Image: Suno
Suno's pitch and the reporting agree on the appeal: signing in and approving a connection is a cleaner route than scraped sessions or resold API access, and it keeps music-making inside the chat a person is already having.
Some things are still open. No separate commercial terms have been announced for tracks made through MCP, so the account's standard plan terms apply, and there are no documented service credentials yet for unattended backends.
Sources · 2