SunoMCP

suno_generate_music

Generate AI music from a text prompt by automatically creating lyrics, melody, style, and arrangement. Use it for quick song ideas when you don't have specific lyrics in mind.

Instructions

Generate AI music from a text prompt using Suno's Inspiration Mode.

This is the simplest way to create music - just describe what you want and Suno
will automatically generate appropriate lyrics, melody, style, and arrangement.

Use this when:
- You want quick music generation with minimal input
- You don't have specific lyrics in mind
- You want Suno to be creative with the arrangement

For full control over lyrics and style, use suno_generate_custom_music instead.

Returns:
    Task ID and generated audio information including URLs, title, lyrics, and duration.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "suno_generate_music"
  }
}

Input Schema

Name	Required	Description	Default
`model`	No	Suno model version. 'chirp-v5-5' is the latest and recommended for best quality with 8-minute max duration. 'chirp-v4-5' is a reliable choice for most use cases. Older models (v3, v3-5, v4) have shorter duration limits.	chirp-v5-5
`prompt`	Yes	Description of the music to generate. Be descriptive about genre, mood, instruments, and theme. Examples: 'A happy birthday song with acoustic guitar', 'Epic orchestral battle music with dramatic choir', 'Chill lo-fi hip hop beat for studying'
`variety`	No	Result diversity: off, normal, high, extra, or max.
`callback_url`	No	Webhook callback URL for asynchronous notifications. When provided, the API will call this URL when the audio is generated.
`instrumental`	No	If true, generate instrumental music without vocals. Default is false (with vocals).
`variation_category`	No	Variation intensity for v5+ models. 'high' for maximum variation, 'normal' for balanced, 'subtle' for minimal changes. Only supported in chirp-v5 and above.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.25Nov 2, 2026

addedInput schema / properties / variety

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "off",
+        "normal",
+        "high",
+        "extra",
+        "max"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Result diversity: off, normal, high, extra, or max.",
+  "title": "Variety"
+}

Changed1 schema field changedv0.1.18Sep 10, 2026

changedInput schema / properties / model / enum

Previous value: -[
-  "chirp-v3-0",
-  "chirp-v3-5",
-  "chirp-v4",
-  "chirp-v4-5",
-  "chirp-v4-5-plus",
-  "chirp-v5",
-  "chirp-v5-5"
-]New value: +[
+  "chirp-v6",
+  "chirp-v6-wild",
+  "chirp-v6-mini",
+  "chirp-v3-0",
+  "chirp-v3-5",
+  "chirp-v4",
+  "chirp-v4-5",
+  "chirp-v4-5-plus",
+  "chirp-v5",
+  "chirp-v5-5"
+]

Addedv0.1.5May 31, 2026
Removedv0.1.3May 24, 2026

Changed1 schema field changedv0.1.1May 6, 2026

addedInput schema / properties / variation_category

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "high",
+        "normal",
+        "subtle"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Variation intensity for v5+ models. 'high' for maximum variation, 'normal' for balanced, 'subtle' for minimal changes. Only supported in chirp-v5 and above.",
+  "title": "Variation Category"
+}

First observedv0.1.0Apr 4, 2026

TDQS

A3.9/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It does disclose key behavior beyond the schema (Suno auto-generates lyrics, melody, style, arrangement) and that a task ID plus audio URLs are returned, but it never explains the asynchronous lifecycle (poll via suno_get_task vs. callback_url), credit cost, or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core verb and mode, then a scannable 'Use this when' list and a single alternative pointer. The 'Returns:' block partially duplicates the existing output schema, which is minor waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and parameter coverage is complete, so the description need only supply purpose, routing, and creative-behavior context, which it does. The main remaining gap is the async task/polling workflow, which an agent would need in order to act on the returned task ID.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all six parameters (model, prompt, variety, callback_url, instrumental, variation_category) are documented in the schema with examples and defaults. The description adds no parameter-level guidance, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Generate AI music from a text prompt') and names the Inspiration Mode, which distinguishes it from the custom-music path. However, the sibling suno_generate_inspo is not addressed, leaving some ambiguity about which 'inspiration' flavor this is.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit 'Use this when' list (quick generation, no lyrics in mind, wants Suno to be creative) and routes the agent to suno_generate_custom_music for full control. This is exactly the when/when-not/alternative structure.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server