suno-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | Your RunAPI API key. Can also be set in ~/.config/runapi/config.json. |
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": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json. |
| convert_audioC | Create a Suno task on RunAPI (convert audio). Returns a task id, status, and output URLs. |
| blend_lyricsB | Create a Suno task on RunAPI (blend lyrics). Returns a task id, status, and result payload. |
| cover_audioC | Create a Suno task on RunAPI (cover audio). Returns a task id, status, and output URLs. |
| create_mashupC | Create a Suno task on RunAPI (create mashup). Returns a task id, status, and output URLs. |
| extend_musicC | Create a Suno task on RunAPI (extend music). Returns a task id, status, and output URLs. |
| generate_lyricsB | Create a Suno task on RunAPI (generate lyrics). Returns a task id, status, and result payload. |
| inspire_musicC | Create a Suno task on RunAPI (inspire music). Returns a task id, status, and output URLs. |
| add_samplesC | Create a Suno task on RunAPI (add samples). Returns a task id, status, and output URLs. |
| visualize_musicC | Create a Suno task on RunAPI (visualize music). Returns a task id, status, and output URLs. |
| remaster_audioC | Create a Suno task on RunAPI (remaster audio). Returns a task id, status, and output URLs. |
| separate_audio_stemsC | Create a Suno task on RunAPI (separate audio stems). Returns a task id, status, and output URLs. |
| stitch_audioC | Create a Suno task on RunAPI (stitch audio). Returns a task id, status, and output URLs. |
| text_to_musicC | Create a Suno task on RunAPI (text to music). Returns a task id, status, and output URLs. |
| text_to_soundC | Create a Suno task on RunAPI (text to sound). Returns a task id, status, and output URLs. |
| generate_personaC | Run a synchronous Suno operation on RunAPI (generate persona). Returns the operation result. |
| boost_styleC | Run a synchronous Suno operation on RunAPI (boost style). Returns the operation result. |
| get_timestamped_lyricsC | Run a synchronous Suno operation on RunAPI (get timestamped lyrics). Returns the operation result. |
| generate_voiceC | Run a synchronous Suno operation on RunAPI (generate voice). Returns the operation result. |
| get_taskB | Fetch the current status and latest result payload for a suno task. |
| check_pricingB | Look up RunAPI pricing for the suno model line. |
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 21 tools
Each tool targets a distinct Suno operation (e.g., text_to_music vs convert_audio vs cover_audio), but the extremely terse descriptions provide little context to differentiate similar-sounding actions like generate_lyrics vs blend_lyrics or text_to_music vs inspire_music. The names themselves are mostly clear, but an agent may still need to infer nuances.
Nearly all tools follow a snake_case verb_noun pattern (convert_audio, generate_lyrics, get_task). Exceptions like login and text_to_music/text_to_sound introduce minor deviations, but overall the naming is predictable and readable.
21 tools is on the higher side, but each corresponds to a distinct Suno API operation, so the count is justified for comprehensive coverage. The set includes auxiliary tools (login, get_task, check_pricing) that round out the workflow without excessive bloat.
The surface covers a wide range of music generation and manipulation tasks, plus task status retrieval and pricing lookup. Minor gaps exist (e.g., no cancel_task or list_tasks), but core create-and-check workflows are fully supported.