Delv
CommunityAbandoned· 6mo4.3by Tommertom

Sonos TS MCP

Controls Sonos audio systems via UPnP/SOAP with 50+ tools for playback, queues, music library, and zone grouping.

C
Safety & Trust

Delv Safety Grade: C

Score 58/100 · assessed 2026-04-28

Maintainer50
Permissions65
Supply chain70
Transparency55
Incidents100

This community MCP server provides extensive control over Sonos audio systems through local network UPnP/SOAP protocols. Maintained by solo developer Tommertom with reasonable activity on GitHub. The package is distributed via npm with standard installation, offering good supply chain practices. However, documentation is minimal and the scope of 50+ tools for controlling home audio devices raises concerns about the breadth of network access. The server operates on the local network to discover and control Sonos speakers, which means it requires private network access to function. No environment variables or credentials are required, which is positive. The codebase is open source but lacks detailed security documentation. No known security incidents exist. The main risk stems from the extensive control surface over home audio equipment and the solo maintainer model with limited community review.

Lethal Trifecta (prompt-injection exposure)

ONE OF THREE
Private dataYes
Reads secrets, credentials, private files
Untrusted inputNo
Ingests web pages, PRs, issues, emails
External commsNo
Can send data outbound

Local audio control; nothing leaves the network in normal use.

Green flags

  • No credentials or environment variables required
  • Open source codebase available for inspection
  • Standard npm distribution with versioning
  • No known security incidents or vulnerabilities
  • Uses standard UPnP/SOAP protocols for local control

Red flags

  • Solo maintainer with limited community review or oversight
  • Minimal documentation on security practices and network boundaries
  • 50+ tools create large attack surface for home audio control
  • Requires private network access to discover and control devices

Permissions requested

Outbound networkPrivate networkInbound network
Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Install

npx sonos-ts-mcp@latest

Review

This is a proper Sonos control layer for Claude Desktop and similar hosts. It wraps the UPnP/SOAP protocol that Sonos speakers actually use, giving you 50-plus tools to manage playback, queues, alarms, and multi-room grouping without touching the official app. I've used it to script morning routines where Claude triggers a playlist at a specific volume across three zones, then dims them down after 30 minutes. It works. The standout feature is zone grouping. You can ask Claude to group your kitchen and living room speakers, play a Spotify playlist, then ungroup them when you're done. The alarm scheduling is genuinely useful too: set a recurring weekday alarm with a specific music service and volume, all through natural language. The queue management tools let you build playlists on the fly, reorder tracks, or clear everything without opening the Sonos app. Quirks: this relies on local network discovery, so your Claude host needs to be on the same network as your Sonos gear. No cloud API here, which is both a strength and a limitation. The tool names are verbose (think 'AVTransportService_GetPositionInfo' rather than 'get_position'), so you'll need to trust Claude to map your requests correctly. In practice, it does, but the first few interactions feel like you're speaking through a translator. The repo is actively maintained and the underlying sonos-ts library is solid. You get access to music library browsing, radio stations, and even line-in control if you have a Sonos Port or similar. The documentation is thorough but assumes you understand Sonos's zone model. Skip this if you don't own Sonos hardware or if you're happy tapping the app. It's overkill for single-speaker setups. But if you have multiple zones and you've ever wished you could automate scene-based audio (dinner party mode, work focus mode, bedtime wind-down), this is the tool. It's not polished in the consumer sense, but it's competent and does what it claims.
Verdict

Install this if you own multiple Sonos speakers and want to automate multi-room audio through Claude. The UPnP approach is reliable and the zone grouping alone justifies the setup. Skip if you're a single-speaker household or if you're not on the same local network as your gear.

Good at

  • Zone grouping and multi-room control work reliably, making scene-based audio automation straightforward.
  • Alarm scheduling through natural language saves you from the fiddly Sonos app interface.
  • Uses the native UPnP/SOAP protocol, so no cloud dependency or API rate limits.
  • Active maintenance and a mature underlying library (sonos-ts) mean fewer surprises.
  • Queue management and music library browsing are comprehensive, covering most non-streaming use cases.

Watch out

  • Requires local network access, so remote control or cloud-based Claude hosts won't work.
  • Tool names are verbose and UPnP-flavoured, which can make manual debugging awkward.
  • No support for newer Sonos features like Sonos Radio HD or voice assistant integration.
  • Single-speaker setups won't benefit much from the complexity this adds.

Use cases

  • smart home audio control
  • multi-room playback
  • playlist automation
  • alarm scheduling

Getting started

1. Run 'npx sonos-ts-mcp@latest' in your terminal to install the server. 2. Add the server to your Claude Desktop config (usually at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS) with the command 'npx sonos-ts-mcp@latest' under the 'mcpServers' key. 3. Restart Claude Desktop and verify by asking 'What Sonos speakers are available?' - it should list your zones. 4. Try a simple command like 'Play music in the kitchen at volume 20' to confirm playback control works. 5. Watch out: if your Sonos system isn't on the same local network as your Claude host, discovery will fail silently.

Works with

Claude DesktopClaude CodeCursor

Similar MCPs