Mcp Dyson Appliances

io.github.m2ai-mcp-serversPublished by GitHub account m2ai-mcp-serversv1.0.0Updated Oct 24, 2026

MCP server for controlling Dyson air purifiers and fans

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

Local MCP server that lets an assistant control Dyson air purifiers and fans through the user's Dyson account.

What you can do
  • Control Dyson air purifiers and fans from the assistant, using the user's own Dyson account.
  • No tool list is published, so the exact commands available are not documented here; the server is described only as controlling purifiers and fans.
  • Account details are supplied through environment variables for email, password and country.
When to use it
Worth adding if you own Dyson air purifiers or fans and want an assistant to operate them from a desktop chat session instead of the Dyson app.
Requirements
Runs as a local process installed from the npm package mcp-dyson-appliances (Node.js needed). Requires a Dyson account: DYSON_EMAIL and DYSON_PASSWORD must be set, and DYSON_COUNTRY (US, GB, DE, FR, AU, CN) selects the region. Desktop only; no web execution.
Before you install
The server needs your Dyson account password in DYSON_PASSWORD, so store it in the local environment rather than in shared configuration. It acts on real household devices, so commands may change fan or purifier settings in your home. Credentials are handled by a third-party package.

Installation

In SourceWeft

  1. Open Mcp Dyson Appliances 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

1
  1. v1.0.0LatestSep 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.