ZoneFoundry for Sonos

dev.zonefoundryPublished by zonefoundry.devOfficial publisherv1.0.9Updated Oct 24, 2026

Control Sonos from any MCP client. No bridge hardware; connects over OAuth — no API key to paste.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

A remote MCP server that lets an assistant control Sonos speakers through an OAuth-connected relay, with no bridge hardware or API key.

What you can do
Control Sonos playback and speakers from an MCP client through the hosted relay service. Connect the assistant to the Sonos setup via OAuth sign-in rather than pasting an API key. No bridge hardware is needed; the connection runs over the remote endpoint.
When to use it
Worth adding when you want an AI assistant to operate Sonos speakers and playback, and you prefer a hosted OAuth connection over local bridge hardware or manual key setup.
Requirements
A remote MCP client that supports streamable HTTP, network access to the relay endpoint, and an OAuth sign-in to authorize the connection. No packages, environment variables or headers are declared.
Before you install
Authorization is granted through OAuth, so review the permissions requested during sign-in. The server relays control of your Sonos devices through a third-party hosted service, so device and playback activity passes through that provider.

Installation

In SourceWeft

  1. Open ZoneFoundry for Sonos in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.zonefoundry%2Fsonos/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "zonefoundry-for-sonos": {
      "type": "http",
      "url": "https://relay.zonefoundry.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.9LatestSep 23, 2026
  2. v1.0.5Sep 18, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.