Smart Speaker Mcp

io.github.WeCodeBasePublished by GitHub account WeCodeBasev1.0.1Updated Oct 24, 2026

Control Google Home and Amazon Alexa speakers from Claude Desktop using natural language.

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

Lets an assistant control Google Home and Amazon Alexa smart speakers from Claude Desktop using natural language.

What you can do
This local MCP server connects Claude Desktop to Google Home and Amazon Alexa speakers so the assistant can issue voice-style commands through natural language. It is distributed as a desktop extension package for macOS (Apple Silicon and Intel). The manifest lists no tools, so the exact command set is not documented here.
When to use it
Worth adding if you already use Google Home or Amazon Alexa devices and want to control them from Claude Desktop instead of a phone app or voice assistant. It is a desktop-only integration, so it is not useful for headless or web-based setups.
Requirements
Runs as a local process on the user's machine via a macOS desktop extension package (Apple Silicon or Intel). No authentication, environment variables, or headers are declared. The speakers and the machine must be on the same network for control to work.
Before you install
No credentials, API keys, or environment variables are declared, but controlling speakers means the assistant can change device state such as playback, volume, or routines. Review what the installed package actually does before granting it control of devices in your home.

Installation

In SourceWeft

  1. Open Smart Speaker Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.