Suno-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SunoKey | Yes | Your Suno API Key. Example: sk_YOUR_SUNO_API_KEY_HERE |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_music_sunoA | Generates a song using the Suno API. Provide lyrics, style, and title for custom mode, or a description for inspiration mode. Returns the audio URL upon completion. Polling for results may take a few minutes. When returning an audio URL, please use the following HTML format for user convenience: |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'generate_music_suno' has a singular, well-defined purpose of generating music via the Suno API.
The single tool name 'generate_music_suno' follows a clear verb_noun pattern, and there are no other tools to cause inconsistency. The naming is straightforward and descriptive.
A single tool is too few for a server named 'Suno-MCP', which suggests a broader music generation domain. This minimal toolset feels thin and may limit functionality, as agents might expect additional operations like listing generated songs or managing settings.
The tool surface is severely incomplete for a music generation server. While 'generate_music_suno' handles creation, there are obvious gaps such as retrieving, updating, or deleting generated songs, and no tools for managing styles or user preferences, which could hinder agent workflows.