SongPilot MCP

Put SongPilot’s Orchestrator (and specialist agents like Visual Director and Publicist) inside the AI tools you already use.

Turn any AI tool into a music team

MCP (Model Context Protocol) is an open standard for securely connecting AI clients to external systems. SongPilot uses MCP to make its Orchestrator and specialist agents available from tools like Claude Desktop and Cursor — without rebuilding your workflow around a new UI.

STEP 1

Create a key

STEP 2

Connect your client

Run the SongPilot MCP adapter and pass your key + workspace id as environment variables.

STEP 3

Ask for outcomes

Ask your AI tool anything — SongPilot will route it through the Orchestrator and specialists.

Works with MCP-compatible clients

SongPilot MCP is designed to work anywhere MCP is supported. Today we provide direct setup instructions for:

Claude Desktop
Cursor
Other MCP hosts (same command + env vars)

Endpoints

The Orchestrator MCP endpoint is:

https://mcp.songpilot.ai/mcp/orchestrator/run

Production: https://mcp.songpilot.ai • Staging: https://mcp-staging.songpilot.ai

Claude Desktop setup

Use the MCP adapter from GitHub: SongPilotAI/songpilot-mcp . Then add the server to your claude_desktop_config.json.

{
  "mcpServers": {
    "songpilot": {
      "command": "node",
      "args": ["/ABS/PATH/TO/songpilot-mcp/src/index.js"],
      "env": {
        "SONGPILOT_API_KEY": "sp_...",
        "SONGPILOT_WORKSPACE_ID": "...",
        "SONGPILOT_MCP_BASE_URL": "https://mcp.songpilot.ai"
      }
    }
  }
}

Tip: keep your API key private. Treat it like a password.

What to ask

“Help me update my artist profile for a release next month.”
“Review my assets and tell me what’s missing for distribution.”
“Generate cover art concepts in the style of … and save the best ones.”

Security

Your SongPilot API key is sensitive. Use a dedicated key per client (e.g. “Claude Desktop”, “Cursor”) so you can revoke access independently.