# Sonos MCP MCP Server > **Sonos MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Sonos MCP. > > MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows, > token refresh, and production-grade auto-scaling — so your AI agents can connect to > third-party services and run freely without you managing any MCP server yourself. > > Server page: https://mewcp.com/mcp/sonos-mcp > MewCP docs: https://docs.mewcp.com > Full catalog: https://mewcp.com/llms.txt --- ## About Sonos MCP lets AI assistants control Sonos speakers and home audio systems by discovering devices, grouping rooms, adjusting volume, managing playback, selecting music sources, and controlling play, pause, skip, and queue operations across compatible speakers. --- ## Details - Server ID: `sonos-mcp` - Version: 1.0.0 - Tools: 34 - Authentication: OAuth, managed by MewCP - Transport: http --- ## Access The gateway URL below serves your **entire MewCP toolset**, not this server on its own. Pasting a config snippet is not enough — Sonos MCP has to be in the toolset first. In order: 1. Add Sonos MCP to your toolset at https://mewcp.com/mcp/sonos-mcp 2. Connect your Sonos MCP account (OAuth); MewCP stores the credential and attaches it to each call 3. Copy your MewCP API key from the dashboard (Developer) 4. Configure your client with the snippet for it below Once connected, an agent does **not** see this server's tools as top-level tools. It sees four meta-tools and reaches everything through them: - `search(query)` — find tools by keyword across the toolset - `get_schema(tools)` — full description and arguments for the tools you picked - `list_accounts(provider)` — only when one app has several connected accounts - `call_tool(server_maskedId, tool_name, args)` — execute So the list below is what `search` can return for this server, not a set of callable tool names on their own. --- ## Tools (34) Descriptions are truncated to 160 characters; call `get_schema` for the full text and the argument schema. Where a tool is annotated, its type is shown — treat `destructive` as irreversible. - `get_households_and_groups_and_players` _(read)_ — Get the household, group, and player IDs every other Sonos tool needs — a discovery of the user's whole Sonos system(s): every household, its groups (each with… - `get_now_playing` _(read)_ — Return what's currently playing on a Sonos group: the source (playlist, station, album, or radio, with its name and type); the current song or track's name,… - `get_shuffle_repeat_crossfade` _(read)_ — Get the shuffle, repeat, and crossfade settings for a Sonos group. Returns shuffle, repeat, repeatOne, and crossfade as booleans. - `set_shuffle_repeat_crossfade` _(write)_ — Change one or more of the shuffle, repeat, and crossfade settings for the content currently playing on a Sonos group: shuffle, repeat, repeat_one, or… - `resume` _(write)_ — Resume playback on a Sonos group — unpause and continue playing. This is the plain 'play'/'resume'/'unpause' action; to start new content, use one of the… - `pause` _(write)_ — Pause playback on a Sonos group — stop the music where it is (it can be resumed). This is the plain 'pause'/'stop' action. IMPORTANT: Stateless command —… - `skip_to_next_track` _(write)_ — Skip to the next track on a Sonos group. Use this when the user asks to skip or play the next track. - `skip_to_previous_track` _(write)_ — Skip to the previous track on a Sonos group. Use this when the user asks to go back or play the previous track. - `seek` _(write)_ — Jump to a specific time in the currently playing track on a Sonos group. Pass position_millis for an absolute target, or delta_millis to fast forward… - `get_player_volume` _(read)_ — Get the volume and mute state of a Sonos player. Group volume and player volume are linked — changing one affects the other. To get the volume of a whole… - `set_player_volume` _(write)_ — Set the volume of a Sonos player to a specific level. Setting a player's volume does not change its mute state. Group volume and player volume are linked —… - `set_player_mute` _(write)_ — Mute or unmute a Sonos player. Group volume and player volume are linked — changing one affects the other. To mute all players in a group, use set_group_mute… - `adjust_player_volume` _(write)_ — Turn a Sonos player's volume up or down by the specified amount. Adjusting a player's volume does not change its mute state. Group volume and player volume are… - `get_group_volume` _(read)_ — Get the volume and mute state of a Sonos group. Group volume is the average level across the group's players. Group volume and player volume are linked —… - `set_group_volume` _(write)_ — Set the volume of a Sonos group to a specific level. Scales all players in the group proportionally, preserving their relative balance — it does not set every… - `set_group_mute` _(write)_ — Mute or unmute all players in a Sonos group. Group volume and player volume are linked — changing one affects the other. To mute a single player, use… - `adjust_group_volume` _(write)_ — Turn a Sonos group's volume up or down by the specified amount. Adjusts all players in the group proportionally, preserving their relative balance — it does… - `get_sonos_favorites` _(read)_ — Get all Sonos favorites saved to a Sonos household. These are items saved within the Sonos app and are distinct from favorites or saved content on any music… - `get_sonos_playlists` _(read)_ — Get all Sonos playlists saved to a Sonos household. These are playlists created in or imported into the Sonos app and are distinct from playlists on any music… - `play_sonos_playlist` _(write)_ — Play a Sonos playlist on a group. Use get_sonos_playlists first to find the playlist ID. For music service playlists use play_playlist instead. - `play_sonos_favorite` _(write)_ — Play a Sonos favorite on a group. Use get_sonos_favorites first to find the favorite ID. - `play_player_line_in` _(write)_ — Play the line-in audio from one Sonos player on a group. Use this when the user wants an external audio source (turntable, record player, CD player, etc.)… - `get_registered_music_services` _(read)_ — List the music services the user has set up for a Sonos household. Call this only to answer informational queries like 'what music services are set up on… - `add_players_to_group` _(write)_ — Add players to a Sonos group. The added players adopt the group's current audio (replacing whatever they were previously playing). Use this for requests like… - `remove_players_from_group` _(write)_ — Remove players from a Sonos group. The removed players stop playing (their previous audio does not resume); the rest of the group continues uninterrupted. Use… - `move_audio_to_players` _(write)_ — Move the audio currently playing on a Sonos group to a new set of players, atomically and with no audio gap. Players in the source group not listed in… - `get_night_sound_and_speech_enhancement` _(read)_ — Get the Night Sound and Speech Enhancement settings for a Sonos player. Speech Enhancement improves TV dialogue and voice clarity; Night Sound reduces loud… - `set_night_sound_and_speech_enhancement` _(write)_ — Set Night Sound and Speech Enhancement for a Sonos player. Speech Enhancement improves TV dialogue and voice clarity; Night Sound reduces loud effects for… - `play_track` _(write)_ — Play a track on a Sonos group. - `play_album` _(write)_ — Play an album on a Sonos group. - `play_artist` _(write)_ — Play a mix of music from an artist on a Sonos group. - `play_playlist` _(write)_ — Play a playlist from a music service on a Sonos group. For Sonos playlists, use play_sonos_playlist instead. - `play_radio` _(write)_ — Play a live broadcast radio station on a Sonos group — a specific, named station the user tunes into, heard as a single continuous stream everyone gets in sync… - `play_station` _(write)_ — Play a personalized, endless station generated from a seed on a Sonos group — something a music service turns into an algorithmic run of tracks (e.g. 'Daft… --- ## Connect Gateway URL: https://gateway.mewcp.com/personal/mcp Every request carries one header: Authorization: Bearer Replace `API_KEY` with your own key from the dashboard (Developer). ## Apps ### Claude Desktop Mac & Windows app - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` - Windows: `%APPDATA%\Claude\claude_desktop_config.json` ```json { "mcpServers": { "mewcp": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "https://gateway.mewcp.com/personal/mcp", "--header", "Authorization:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open Claude Desktop → Settings → Developer → "Edit Config" 2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one) 3. Save the file, then quit Claude Desktop completely and reopen it 4. Start a new conversation — your tool will be available ### VS Code Copilot / Cline - Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead. ```json { "mcp.servers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have a "servers" section in your mcp.json? Just add the server entry inside it. 1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P) 2. Run "MCP: Open User Configuration" to open your mcp.json 3. Paste the snippet and save 4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat ### Cursor AI-first editor - macOS: `~/.cursor/mcp.json` - Windows: `%USERPROFILE%\.cursor\mcp.json` ```json { "mcpServers": { "mewcp": { "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it. 1. Open Cursor → Settings → Cursor Settings → MCP 2. Click "Add new global MCP server" 3. Paste the snippet and save 4. Restart Cursor ### Codex OpenAI's CLI agent - Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers. 1. Open your Codex MCP config or project-level config file 2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects 3. Save the file and restart Codex 4. Verify the tool is available inside a fresh session ### Claude Code Anthropic's CLI agent - ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file and start (or restart) Claude Code 4. Or skip the file entirely and run the CLI command below instead ### OpenCode Open-source terminal agent - ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist. ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "mewcp": { "type": "remote", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcp" section in your opencode.json? Just add the server entry inside it. 1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and start (or restart) OpenCode ### OpenClaw Self-hosted agent gateway - ~/.openclaw/openclaw.json — create it if it doesn't exist. ```json { "mcp": { "servers": { "mewcp": { "transport": "streamable-http", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } } ``` Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers". 1. Open ~/.openclaw/openclaw.json in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and restart OpenClaw ### Antigravity Google's agentic IDE - ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist. ```json { "mcpServers": { "mewcp": { "serverUrl": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported. 1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager) 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file — the server connects automatically ### Hermes Nous Research's CLI agent - config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key. ```yaml mcp_servers: mewcp: url: "https://gateway.mewcp.com/personal/mcp" headers: Authorization: "Bearer API_KEY" ``` Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it. 1. Open config.yaml in your Hermes config directory 2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any) 3. Save the file, then run /reload-mcp in Hermes (or start a fresh session) 4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected ### DeepSeek Harness DeepSeek's agent harness - cordis.yml in your DSH project — or the patch file you mount plugins from. ```yaml - id: mcp-mewcp name: '@deepseek-ai/dsh-mcp-client' config: serverName: mewcp transport: streamable-http url: https://gateway.mewcp.com/personal/mcp headers: Authorization: "Bearer API_KEY" ``` One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry. 1. Open cordis.yml (or your patch file) in your DSH project 2. Paste the entry into your plugin list, keeping the leading dash and indentation 3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__ 4. Verify with: dsh web --dump-config | grep -A3 mcp ## SDKs ### Python fastmcp client ```python import asyncio from fastmcp import Client from fastmcp.client.transports import StreamableHttpTransport SERVER_URL = "https://gateway.mewcp.com/personal/mcp" API_KEY = "API_KEY" transport = StreamableHttpTransport( url=SERVER_URL, headers={ "Authorization": f"Bearer {API_KEY}", } ) async def main(): client = Client(transport) async with client: tools = await client.list_tools() print(tools) asyncio.run(main()) ``` 1. Install fastmcp: pip install fastmcp 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run your script ### TypeScript MCP SDK ```typescript import { Client } from "@modelcontextprotocol/sdk/client/index.js"; import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"; const SERVER_URL = "https://gateway.mewcp.com/personal/mcp"; const API_KEY = "API_KEY"; const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), { requestInit: { headers: { Authorization: `Bearer ${API_KEY}`, }, }, }); const client = new Client({ name: "mewcp-client", version: "1.0.0" }); await client.connect(transport); const tools = await client.listTools(); console.log(tools.tools.map((t) => t.name)); ``` 1. Install: npm install @modelcontextprotocol/sdk 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)