ZoneFoundry for Sonos vs io.github.WeCodeBase/smart-speaker-mcp
ZoneFoundry for Sonos is an MCP server published by zonefoundry.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.WeCodeBase/smart-speaker-mcp is an MCP server published by WeCodeBase. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.9 No figure published Not marked · First seen |
Listed Version: 1.0.1 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ZoneFoundry for Sonos | io.github.WeCodeBase/smart-speaker-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (relay.zonefoundry.dev/mcp) | On your machine (https://github.com/WeCodeBase/smart-speaker-mcp/releases/download/v1.0.0/smart-speaker-mcp-darwin-arm64) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 23 h ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
ZoneFoundry for Sonos
Control Sonos from any MCP client. No bridge hardware; connects over OAuth — no API key to paste.
io.github.WeCodeBase/smart-speaker-mcp
Control Google Home and Amazon Alexa speakers from Claude Desktop using natural language.
How to run each
ZoneFoundry for Sonos As a remote MCP server
claude mcp add --transport http sonos https://relay.zonefoundry.dev/mcpio.github.WeCodeBase/smart-speaker-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only ZoneFoundry for Sonos has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: ZoneFoundry for Sonos · What it can do: io.github.WeCodeBase/smart-speaker-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.