suno-v6-kie-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_HOST | No | HTTP host for remote MCP | 127.0.0.1 |
| MCP_HTTP_PORT | No | HTTP port for remote MCP | 3000 |
| MCP_TRANSPORT | No | Transport mode: 'http' for remote MCP, otherwise stdio | stdio |
| KIE_AI_API_KEY | Yes | Bearer API key for Kie.ai | |
| KIE_AI_BASE_URL | No | Base URL for the Kie.ai API | https://api.kie.ai |
| MCP_ALLOWED_HOSTS | No | Allowed public host/domain for remote MCP (required for remote HTTP) | |
| KIE_MCP_HTTP_TOKEN | No | Bearer token for MCP client authentication (required for remote HTTP) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| suno_generate_musicB | Generate a song or instrumental track using Kie.ai Suno V6, V6_MINI, or V6_WILD. The returned task_id can be checked with suno_get_task_status. |
| suno_get_task_statusA | Get the current status and generated audio URLs for a Kie.ai Suno task. |
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 2 tools
The two tools have clearly distinct purposes: one initiates music generation and returns a task ID, while the other retrieves status and generated audio URLs for that task. There is no overlap or ambiguity between them.
Both tool names follow the same suno_ prefix with a clear verb_noun pattern: generate_music and get_task_status. The naming is consistent, descriptive, and predictable.
With only two tools, the server is minimal but appropriately scoped for an asynchronous generation workflow: submit a task and check its result. It is slightly thin, but each tool serves an essential role.
The core lifecycle of submitting a generation task and polling for results is covered. Minor gaps exist, such as no cancel or list operations, but for a focused Suno generation server these are not critical.