Music Media MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_and_merge_mediaA | Generates a music video by combining AI-generated audio with the source image or video. Args: source_media_url: A publicly accessible URL to a source image or video. music_prompt: Optional music description. If omitted, Gemini generates one. IMPORTANT: The output of this tool is valid HTML. You MUST display this output to the user by generating a generic HTML Artifact containing the exact code returned by the tool. |
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
Only one tool exists, so there is no possibility of confusion with other tools.
With a single tool, naming consistency is trivially maintained. The name uses snake_case and is descriptive.
A single tool for a 'Music Media MCP Server' is too few; the server likely requires multiple tools for different media operations.
The tool surface is severely incomplete, lacking separate functionalities for audio generation, video processing, or result retrieval.