Skip to content

Adding a Server

SendSpin Player uses a step-by-step wizard to configure your server connection. The wizard adapts based on your choices, so you only see options relevant to your setup.

From the Server List screen, tap the + button in the bottom-right corner to launch the Add Server wizard.

Choose your server type:

  • SendSpin Only — Connect to a standalone SendSpin server for synchronized audio playback
  • Music Assistant — Connect to a Music Assistant instance for library browsing, search, playlists, and synchronized playback

The app can discover servers on your local network automatically using mDNS/Zeroconf:

  • Auto-discovered servers appear in a list as they’re found
  • Manual entry — If your server doesn’t appear, enter the IP address or hostname and port (default: 8927)

The app will test the connection before proceeding.

Choose how you’ll access this server:

  • Local network only — You’re always on the same WiFi as the server
  • Remote access needed — You want to connect from outside your home network

If you choose remote access, you’ll configure a Remote ID or Reverse Proxy in the next steps.

If you chose remote access:

  • Remote ID — Scan a QR code from your Music Assistant settings or enter the 26-character Remote ID manually
  • Reverse Proxy — Enter your proxy URL and authentication credentials

Step 5: Music Assistant Login (if applicable)

Section titled “Step 5: Music Assistant Login (if applicable)”

If you selected Music Assistant as your server type:

  1. Enter your Music Assistant credentials
  2. The app tests the connection to the Music Assistant API
  3. Configure the Music Assistant port (default: 8095)
  1. Review all configured connection methods
  2. Enter a nickname for this server (e.g., “Living Room”, “Home Server”)
  3. Tap Save to add the server

Long-press a server in the server list and select Set as Default. The default server is used for auto-start on boot.

Long-press a server to access the edit and delete options.

When a server has multiple connection methods configured, the app automatically selects the best available method:

  1. Local — Used when on the same network (lowest latency)
  2. Proxy — Used when local is unavailable but proxy is configured
  3. Remote — Used as a fallback via WebRTC