Home Assistant MCP vs Sonos Ts MCP
A side-by-side look at the Home Assistant MCP and Sonos Ts MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
H
Home Assistant MCPHome Automation · Local subprocess (stdio)Home Assistant and ESPHome for coding agents: states, services, automations, dashboards, flashing.56GoodAuth: not declaredVerdict: choose Home Assistant MCP for home automation work as a local process; choose Sonos Ts MCP for home automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
HChoose Home Assistant MCP when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
ha_get_config, ha_list_entities, ha_get_state.
Choose Sonos Ts MCP when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
sonos_agent, sonos_discover, sonos_add_device.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | H Home Assistant MCP | |
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 56/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 15 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 80 | 60 |
| Full listing | View Home Assistant MCP | View Sonos Ts MCP |
Tools & capabilities
Home Assistant MCP tools 80
ha_get_configCore config: version, location, time zone, loaded components.ha_list_entitiesList entities (filter by domain, free-text search, area).ha_get_stateFull state + attributes for one or more entities.ha_get_historyHistorical state changes over a time window. Given only a start time, it runs up to now (Home Assistant alone stops 24 hours after the start); `ha_get_logbook` does the same.ha_list_servicesAvailable services (and their fields for a given domain).ha_list_areasAreas (rooms/zones).ha_list_devicesDevice registry (filter by area / search).ha_get_entity_registryRegistry metadata: platform, area, device, disabled/hidden.ha_render_templateRender a Jinja2 template against live state.ha_list_helpersList stored helpers (input_boolean, input_number, counter, timer, …).ha_list_automationsAutomations with entity_id, unique id, state, last-triggered.ha_get_automationFull automation config (triggers/conditions/actions).- +68 more on the listing page
Sonos Ts MCP tools 60
sonos_agentAI-powered natural language control. Give instructions like "Play jazz in the living room" and the agent autonomously handles device discovery, tool selection, and execution. Only available when `OPENAI_API_KEY` or `GOOGLE_GENERATIVE_AI_API_KEY` is configured. See [Agent Tool Documentation](./docs/…sonos_discoverDiscover Sonos devices on the network using SSDP multicastsonos_add_deviceManually add a Sonos device by IP address (useful when SSDP discovery fails)sonos_list_devicesList all discovered/registered devicessonos_playStart playbacksonos_pausePause playbacksonos_stopStop playbacksonos_nextSkip to next tracksonos_previousSkip to previous tracksonos_set_volumeSet volume (0-100)sonos_get_volumeGet current volumesonos_set_muteMute or unmute- +48 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Home Assistant MCP
{
"mcpServers": {
"home-assistant-mcp-2": {
"command": "npx",
"args": [
"-y",
"@vortitron/home-assistant-mcp"
]
}
}
}
Sonos Ts MCP
{
"mcpServers": {
"tommertom-sonos-ts-mcp": {
"command": "npx",
"args": [
"-y",
"sonos-agent-cli"
]
}
}
}
Frequently asked questions
Home Assistant MCP is categorized under Home Automation and uses a local stdio subprocess. Sonos Ts MCP belongs to Home Automation and uses a local stdio subprocess. Pick Home Assistant MCP for home automation work and Sonos Ts MCP for home automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Home Assistant MCP has no declared pricing — check the project's own site. Sonos Ts MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add home-assistant-mcp-2 and tommertom-sonos-ts-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Home Assistant MCP has a quality signal of 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Sonos Ts MCP has 56/100 (Good) with 3 views, 0 installs and 15 GitHub stars.