Sonos makes multi-room wireless speakers and sound systems, controlled through the Sonos app or, now, through AI assistants.
Agen.co connects to Sonos through Sonos's own hosted MCP server as an Official connector. Each user authorizes with their own Sonos account, and agents can only reach that user's own Sonos system.
Prerequisites
Prerequisites
- A Sonos account with an existing Sonos system set up at home (at least one player registered to a household). There is no sandbox or demo system — authorization connects to the user's real speakers, and a command plays or changes settings on them immediately.
- The Sonos account holder must be at least 18 years old, per Sonos's MCP terms.
- No app needs to be registered with Sonos — the MCP server registers Agen.co as a client automatically, so there is no Client ID or Client Secret to copy.
In the Agen.co portal, go to Connectors → My connectors and click Add connector.
In the Select connector drawer, search for
Sonosand select it. The Add Sonos panel opens.Fill in the field:
Field Required Description Instance Slug Yes Prefixes each imported tool as slug__tool, so several instances of the connector can coexist. Prefilled withsonos, or with the next free slug such assonos-2if Sonos is already connected. Use lowercase kebab-case. You can change it later from the connector's settings.Click Connect. Sonos opens in a new tab, and the panel shows Waiting for authorization — complete it in the opened tab…
On the Authorize access to Sonos screen, sign in if prompted, then review the request — shown as coming from an app named MCP Client — and click Approve. The screen lists what it can do: play and control music (tracks, volume, grouping, favorites, and playlists), and see which music services are connected to the account.
Back in Agen.co, the panel switches to Select the tools to import from Sonos. Every tool is toggled on; turn off any you don't want to import, then click Add.
The connector is created and its tools imported only when you click Add. If you close the panel before that, nothing is saved, even though the Sonos tab reported success.
Adding the connector doesn't authorize anyone's tool calls yet. The first time each user's agent calls a Sonos tool, the call returns an authorization link instead of a result. The user opens the link and approves the same way. After that, the user's tool calls reach only that user's own Sonos system — connecting the MCP doesn't grant access to anyone else's speakers.
Once connected, Sonos appears under My connectors with 34 tools spanning:
| Area | What it covers |
|---|---|
| Discovery | Reading every household, group, and player on the account, with each player's capabilities — the IDs every other tool needs |
| Now playing | Reading what's currently playing on a group: track, album, artist, station, or stream |
| Playback control | Pausing, resuming, skipping to the next or previous track, and seeking within a track |
| Starting playback | Playing an album, artist, track, music-service playlist, live radio station, algorithmic station, Sonos favorite, Sonos playlist, or a player's line-in audio |
| Grouping and multi-room | Adding or removing players from a group, and moving playing audio from one set of players to another |
| Volume and mute | Reading and setting volume and mute state, per player or per group |
| Sonos favorites and playlists | Listing favorites and playlists saved in the Sonos app |
| Music services | Listing which music services are connected to the household |
| Shuffle, repeat, and crossfade | Reading and changing these playback settings for a group |
| Home theater settings | Reading and changing Night Sound and Speech Enhancement on soundbar players |
Enabling the Sonos connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.