Skip to main content
Glama
amCharlie

MusicMCP.AI

by amCharlie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MUSICMCP_API_KEYYesYour MusicMCP.AI API key
MUSICMCP_API_URLNoMusicMCP.AI API base URLhttps://www.musicmcp.ai/api
TIME_OUT_SECONDSNoTimeout for music generation in seconds600

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

NameDescription
generate_prompt_songA

🎼 Inspiration Mode: Generate songs based on simple text descriptions (AI automatically generates title, lyrics, style, etc.)

Use case: Use when users only provide simple song themes or emotional descriptions without detailed specifications.

Example inputs:
- "Help me generate a song about a peaceful morning"
- "Want a song that expresses longing"
- "Create music about friendship"

⚠️ COST WARNING: This tool makes an API call to MusicMCP.AI which may incur costs (5 credits per generation). Each generation creates 2 songs. Only use when explicitly requested by the user.

Language Note: Pass the prompt in the user's input language.

Args:
    prompt (str): Song theme or emotional description, 1-1200 characters
    instrumental (bool): Whether instrumental only (no lyrics)
    style (str, optional): Music style (e.g., "ambient", "pop", "rock"), default None

Returns:
    Song information including download URLs
generate_custom_songA

🎵 Custom Mode: Generate songs based on detailed song information (user specifies song name, lyrics, style, etc.)

Use case: Use when users provide detailed song information including song name, complete lyrics, and style.

Example inputs:
- "Song name: Summer of Cicada Shedding, Lyrics: [complete lyrics], style: folk"

⚠️ COST WARNING: This tool makes an API call to MusicMCP.AI which may incur costs (5 credits per generation). Each generation creates 2 songs. Only use when explicitly requested by the user.

Language Note: Pass the title and lyrics in the user's input language.

Args:
    title (str): Song title, required
    lyric (str, optional): Complete lyrics content, not required when instrumental is True
    tags (str, optional): Music style tags (e.g., 'pop', 'rock', 'folk')
    instrumental (bool): Whether instrumental only (no lyrics)

Returns:
    Song information including download URLs
check_credit_balanceB

Check your credit balance.

check_api_healthA

Check the health status of the MusicMCP.AI API service.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 4 tools

Disambiguation5/5

The four tools have clearly distinct purposes: check_api_health monitors service status, check_credit_balance queries account credits, generate_custom_song creates songs from detailed specifications, and generate_prompt_song generates songs from simple themes. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (check_api_health, check_credit_balance, generate_custom_song, generate_prompt_song). The naming is uniform and predictable, using snake_case throughout with clear action-object pairs that enhance readability and usability.

Tool Count4/5

With 4 tools, the count is reasonable for a music generation service, covering essential operations like health checks, balance inquiries, and two song generation modes. However, it feels slightly thin as it lacks tools for managing generated songs (e.g., list, delete) or handling credits beyond checking balance, which could limit functionality in extended workflows.

Completeness3/5

The toolset covers core song generation and basic service operations, but has notable gaps. There are no tools for managing generated songs (e.g., retrieval, deletion), handling credits (e.g., purchase, usage history), or configuring settings. This incompleteness may require workarounds for agents, especially in scenarios involving song lifecycle management or credit transactions.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources