ProducerMCP

# ProducerMCP

<!-- mcp-name: io.github.AceDataCloud/mcp-producer -->

[![PyPI version](https://img.shields.io/pypi/v/mcp-producer.svg)](https://pypi.org/project/mcp-producer/)
[![PyPI downloads](https://img.shields.io/pypi/dm/mcp-producer.svg)](https://pypi.org/project/mcp-producer/)
[![Python 3.10+](https://img.shields.io/badge/python-3.10+-blue.svg)](https://www.python.org/downloads/)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
[![MCP](https://img.shields.io/badge/MCP-Compatible-green.svg)](https://modelcontextprotocol.io)

A [Model Context Protocol (MCP)](https://modelcontextprotocol.io) server for AI music generation using [Producer/Riffusion](https://www.riffusion.com/) (FUZZ models) through the [AceDataCloud API](https://platform.acedata.cloud?utm_source=github&utm_medium=referral&utm_campaign=evergreen&utm_content=producer_mcp_readme_platform).

Generate AI music directly from Claude, VS Code, or any MCP-compatible client.

## Features

- **Text to Music** - Create AI-generated music from text prompts
- **Custom Music** - Full control with custom lyrics, title, and style
- **Song Extension** - Continue songs from any timestamp
- **Cover/Remix** - Create covers in different genres and styles
- **Variations** - Generate alternative versions of songs
- **Vocal/Instrumental Swap** - Mix vocals and instrumentals between songs
- **Section Replacement** - Re-generate specific sections of a song
- **Stem Separation** - Split songs into vocal and instrumental tracks
- **Lyrics Generation** - Generate structured lyrics from prompts
- **Video Generation** - Create music videos for songs
- **WAV Export** - Get lossless audio format
- **8 FUZZ Models** - From FUZZ-0.8 to FUZZ-2.0 Pro

## Tool Reference

| Tool | Description |
|------|-------------|
| `producer_generate_music` | Generate AI music from a text prompt. |
| `producer_generate_custom_music` | Generate music with custom lyrics, title, and style. |
| `producer_extend_music` | Extend an existing song from a specific timestamp. |
| `producer_cover_music` | Create a cover/remix version in a different style. |
| `producer_variation_music` | Create a variation of an existing song. |
| `producer_swap_vocals` | Swap vocals between two songs. |
| `producer_swap_instrumentals` | Swap instrumentals between two songs. |
| `producer_replace_section` | Replace a specific time range with new content. |
| `producer_stems_music` | Separate a song into vocal and instrumental stems. |
| `producer_generate_lyrics` | Generate structured song lyrics from a prompt. |
| `producer_upload_audio` | Upload external audio for processing. |
| `producer_generate_video` | Generate a music video for a song. |
| `producer_generate_wav` | Get lossless WAV format of a song. |
| `producer_get_task` | Query the status of a generation task. |
| `producer_get_tasks_batch` | Query multiple generation tasks at once. |
| `producer_list_models` | List all available FUZZ models. |
| `producer_list_actions` | List all available actions and tools. |
| `producer_get_lyric_format_guide` | Get lyrics formatting guide. |

## Connect: hosted OAuth, API token, or local stdio

The hosted endpoint is `https://producer.mcp.acedata.cloud/mcp`. Choose one route for the MCP client:

| Route | When to use it | Credential setup |
|---|---|---|
| Hosted OAuth | The client supports remote MCP OAuth | Add only the URL, then sign in to AceDataCloud and approve access. No token needs to be pasted into client configuration. |
| Hosted API token | The client cannot finish OAuth, or you need an explicit integration credential | Send an AceDataCloud API token in the `Authorization: Bearer …` header. Keep it in a local secret store or environment variable. |
| Local stdio | The client runs a local MCP process | Install `mcp-producer` and pass `ACEDATACLOUD_API_TOKEN` to that process. It still calls the AceDataCloud API. |

The hosted service advertises OAuth metadata and Dynamic Client Registration (DCR). **DCR registers the client application; it is not an API key.** OAuth signs you in and the client sends the resulting Bearer token; it may reuse or create an API credential for the account. Browser sign-in still requires an AceDataCloud account. The hosted service can be metered: review [current service documentation](https://platform.acedata.cloud/documents/producer?utm_source=github&utm_medium=referral&utm_campaign=evergreen&utm_content=producer_mcp_readme_quick_start) and displayed pricing before a real operation. Do not configure both an OAuth login and a fixed `Authorization` header for the same server.

### Hosted OAuth examples

- **Claude and Claude Desktop chat:** Add a remote custom connector in `Customize → Connectors → Add custom connector`, enter `https://producer.mcp.acedata.cloud/mcp`, select sign-in, and choose **Register automatically** if Claude asks how to register its OAuth client. Complete consent. Claude Desktop's local `claude_desktop_config.json` is a separate setup. [Claude connector guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).
- **Claude Code:** `claude mcp add --transport http --scope user producer https://producer.mcp.acedata.cloud/mcp`, then `claude mcp login producer`. Check `/mcp`. [Claude Code MCP guide](https://code.claude.com/docs/en/mcp).
- **Cursor:** Add a remote server with only `https://producer.mcp.acedata.cloud/mcp`. For a project, merge the entry below into `<project>/.cursor/mcp.json`; for personal use, use `~/.cursor/mcp.json`. [Cursor MCP guide](https://cursor.com/docs/mcp).
- **VS Code / Copilot:** Run **MCP: Add Server**, select HTTP, enter `https://producer.mcp.acedata.cloud/mcp`, then finish the browser sign-in. New portable workspace configs use `<project>/.mcp.json`; the VS Code-specific format below uses `<project>/.vscode/mcp.json` or the user profile. Check **MCP: List Servers**. [VS Code MCP setup](https://code.visualstudio.com/docs/agent-customization/mcp-servers).
- **Codex:** `codex mcp add producer --url https://producer.mcp.acedata.cloud/mcp`, then `codex mcp login producer`. Its user settings are in `~/.codex/config.toml`. [Official Codex MCP guide](https://developers.openai.com/codex/mcp/).

Cursor project config (OAuth):

```json
{
  "mcpServers": {
    "producer": {"url": "https://producer.mcp.acedata.cloud/mcp"}
  }
}
```

VS Code-specific workspace config (OAuth):

```json
{
  "servers": {
    "producer": {"type": "http", "url": "https://producer.mcp.acedata.cloud/mcp"}
  }
}
```

### Hosted API token

Sign in at [AceDataCloud Platform](https://platform.acedata.cloud?utm_source=github&utm_medium=referral&utm_campaign=evergreen&utm_content=producer_mcp_readme_platform), open the [service page](https://platform.acedata.cloud/documents/producer?utm_source=github&utm_medium=referral&utm_campaign=evergreen&utm_content=producer_mcp_readme_quick_start), and obtain an API credential. A fixed Bearer header is useful when your client lacks OAuth; an invalid header does not fall back to OAuth in Claude Code. The header value is sensitive, so keep it out of committed files and screenshots.

For Claude Code, the shell expands the token when you add the server; treat the saved user MCP config as a secret:

```bash
export ACEDATACLOUD_API_TOKEN='YOUR_API_TOKEN'
claude mcp add --transport http --scope user producer https://producer.mcp.acedata.cloud/mcp \
  --header "Authorization: Bearer $ACEDATACLOUD_API_TOKEN"
```

For a Claude Code project config, put a variable reference in `<project>/.mcp.json` and set that variable in the environment that launches Claude Code:

```json
{
  "mcpServers": {
    "producer": {
      "type": "http",
      "url": "https://producer.mcp.acedata.cloud/mcp",
      "headers": {"Authorization": "Bearer ${ACEDATACLOUD_API_TOKEN}"}
    }
  }
}
```

Cursor uses a different environment-variable syntax in `~/.cursor/mcp.json` or an uncommitted project config:

```json
{
  "mcpServers": {
    "producer": {
      "url": "https://producer.mcp.acedata.cloud/mcp",
      "headers": {"Authorization": "Bearer ${env:ACEDATACLOUD_API_TOKEN}"}
    }
  }
}
```

In VS Code, run **MCP: Open User Configuration** and merge this server plus its masked input; `${input:...}` is for VS Code's user/workspace format and is not portable to the Agent Host `.mcp.json` format:

```json
{
  "inputs": [
    {"id": "acedata-producer-token", "type": "promptString", "description": "AceDataCloud API token", "password": true}
  ],
  "servers": {
    "producer": {
      "type": "http",
      "url": "https://producer.mcp.acedata.cloud/mcp",
      "headers": {"Authorization": "Bearer ${input:acedata-producer-token}"}
    }
  }
}
```

For **Cline**, use its MCP configuration UI or CLI file `~/.cline/data/settings/cline_mcp_settings.json`; its remote transport value is `streamableHttp`. For **JetBrains AI Assistant**, add a remote URL from **Settings → Tools → AI Assistant → Model Context Protocol (MCP)**. For **Zed**, use a `context_servers` entry with the URL only for OAuth or add a local Bearer header. These clients have different configuration schemas; follow their current UI rather than copying another client's JSON. [Cline](https://docs.cline.bot/mcp/mcp-overview) · [JetBrains](https://www.jetbrains.com/help/ai-assistant/mcp.html) · [Zed](https://zed.dev/docs/ai/mcp).

### Local stdio

Install the package and give the local process an API token:

```bash
python -m pip install mcp-producer
export ACEDATACLOUD_API_TOKEN='YOUR_API_TOKEN'
mcp-producer
```

For Claude Desktop local MCP, merge this entry into the file opened by its developer settings (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS). `uvx` requires [uv](https://docs.astral.sh/uv/) on `PATH`:

```json
{
  "mcpServers": {
    "producer": {
      "command": "uvx",
      "args": ["mcp-producer"],
      "env": {"ACEDATACLOUD_API_TOKEN": "YOUR_API_TOKEN"}
    }
  }
}
```

Ke