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_taskA | 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
Most tools target a distinct Suno operation (extend_music, cover_audio, remaster_audio, separate_audio_stems), so an agent can generally pick the right one. However, several tools (text_to_music vs text_to_sound, generate_lyrics vs blend_lyrics vs get_timestamped_lyrics, generate_voice) have closely related names, and the sync tools' descriptions are generic boilerplate that gives no extra differentiation.
All 21 names are snake_case and follow a verb_noun or verb_to_noun pattern (get_task, create_mashup, text_to_music, separate_audio_stems), with the sole prefix landing on 'get_' for retrieval tools. No mixed conventions or casing deviations.
21 tools sits in the heavy range, but each maps to a genuinely distinct Suno API operation rather than redundant wrappers, so consolidation isn't obviously possible. Slightly over the ideal band, but not bloated with filler.
The surface covers the full creation lifecycle (many generation/transform operations), plus auth (login), status polling (get_task), and pricing (check_pricing). Minor gaps: no task cancellation/delete or list-of-tasks operation, which an agent may want for managing queued jobs.