Suno MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUNO_DEBUG | No | Set to 1 for debug logging | |
| SUNO_CDP_URL | No | Connect to existing Chrome via CDP (e.g., http://localhost:9222) | |
| SUNO_HEADLESS | No | Must be false for generation | false |
| SUNO_BROWSER_PROFILE_DIR | No | Persistent browser profile directory | ~/.suno-mcp/browser-profile |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| suno_get_creditsA | Check your Suno account credit balance (uses your logged-in suno.com session). |
| suno_get_recentB | List your recent Suno songs from your account library. |
| suno_generate_songA | Generate a song with custom lyrics and style (Custom Mode). Opens/uses a browser with your Suno login. Generation runs through suno.com so no third-party API is needed. Returns clip IDs — use suno_wait_for_songs to poll. |
| suno_generate_from_descriptionA | Generate a song from a text description (Simple/Inspiration Mode). Suno writes the lyrics automatically. |
| suno_check_statusB | Check generation status for one or more song IDs. |
| suno_wait_for_songsA | Wait until songs finish generating (up to 3 minutes), then return audio URLs. |
| suno_download_songA | Download a completed song as MP3 to a local folder. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: checking status, downloading, generating from description or custom mode, checking credits, listing recent songs, and waiting for generation. The two generate tools are well-differentiated by simple vs. custom mode with auto vs. user-provided lyrics and style.
All tools follow a consistent 'suno_verb_noun' pattern with lowercase and underscores (e.g., suno_check_status, suno_generate_song). The naming is predictable and clearly indicates each tool's action and target.
With 7 tools, the server is well-scoped for managing Suno song generation. Each tool serves a necessary function without redundancy or bloat, covering generation, status, download, credits, and listing.
The tool set covers the core song creation lifecycle: generating (two modes), monitoring status, downloading, checking credits, and listing recent songs. Missing features like canceling generation or deleting songs are minor gaps that don't severely hinder typical workflows.