MCP MiniMax Music Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIML_API_KEY | Yes | Your AIML API key (must be prefixed with 'Bearer ') |
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 |
|---|---|
| generate_audioB | Generate audio using AIML API. The process has two steps: 1) Submit generation request 2) Get the generated audio. If generation_id is not provided, it will start a new generation. |
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 single tool 'generate_audio' has a clear, distinct purpose.
The single tool name follows a clear verb_noun pattern (generate_audio), and with only one tool, consistency is inherently perfect as there are no other names to compare against.
One tool is too few for a music server's apparent scope, which typically involves operations like listing, playing, or managing audio beyond just generation. This minimal set limits functionality and feels incomplete for the domain.
The tool surface is severely incomplete for a music server. It only covers audio generation, with no tools for retrieving, updating, deleting, or managing audio files, creating significant gaps that will cause agent failures in typical music-related tasks.