Ai Music Mcp

Created By
AIMUSICMCP7 months ago
The World's First AI Music MCP Beyond images and video, your agent can now generate music.
Overview

What is Ai Music Mcp?

Ai Music Mcp is the world's first AI music generation platform that allows users to create music using natural language commands.

How to use Ai Music Mcp?

To use Ai Music Mcp, obtain an API key from the MusicMCP.AI platform, install the necessary tools, and configure your environment to start generating music.

Key features of Ai Music Mcp?

  • 🎼 AI Music Generation based on text prompts.
  • 🎵 Dual Generation Modes: Inspiration mode and Custom mode.
  • 🔗 Direct Download Links for generated music.
  • 🎹 Options for instrumental-only music or full songs with vocals.
  • ✅ Credit Balance Check and API Health Monitoring.

Use cases of Ai Music Mcp?

  1. Generating songs based on user-defined themes.
  2. Creating custom music with specific lyrics and styles.
  3. Checking API service health and credit balance.

FAQ from Ai Music Mcp?

  • Can I generate music in different styles?

Yes! You can specify styles like pop, rock, ambient, etc.

  • Is there a cost to use Ai Music Mcp?

Yes, generating music costs credits, but checking your balance and API health is free.

  • How do I check my credit balance?

You can use the 'Check Credit Balance' tool to see your remaining credits.

Server Config

{
  "mcpServers": {
    "MusicMCP.AI": {
      "command": "uvx",
      "args": [
        "aimusic-mcp"
      ],
      "env": {
        "MUSICMCP_API_KEY": "<your-api-key>",
        "MUSICMCP_API_URL": "https://www.musicmcp.ai/api",
        "TIME_OUT_SECONDS": "600"
      }
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
AIMUSICMCP
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago