Musicwire MCP Server

What the code does

We read the source, 2 d ago · rules 995398eba69f

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

      const destination = path.join(this.directory, hash);

    execFileSync(command, args, { stdio: 'ignore' });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add musicwire-mcp -- npx -y musicwire-mcp

{
  "mcpServers": {
    "musicwire-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "musicwire-mcp"
      ]
    }
  }
}

[mcp_servers.musicwire-mcp]
command = "npx"
args = ["-y", "musicwire-mcp"]

{
  "mcpServers": {
    "musicwire-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "musicwire-mcp"
      ]
    }
  }
}

{
  "servers": {
    "musicwire-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "musicwire-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: MUSICWIRE_API_URL (Musicwire API base URL), MUSICWIRE_X402_PRIVATE_KEY (Throwaway buyer key funded with USDC on the API's advertised network).