Mcp Dyson Appliances
Control Dyson purifiers and fans from your coding agent for home-office automation demos or personal IoT integrations.
Overview
mcp-dyson-appliances is a MCP server for the Build phase that controls Dyson air purifiers and fans through your Dyson account from an agent.
What is this MCP server?
- MCP control for Dyson air purifiers and fans via Dyson account credentials
- Required env: DYSON_EMAIL, DYSON_PASSWORD; optional DYSON_COUNTRY (US, GB, DE, FR, AU, CN)
- npm package mcp-dyson-appliances v1.0.0 with stdio transport
- Brings consumer IoT into the same MCP stack as your dev tools
- Useful for automation skills, smart-home side projects, and integration prototypes
- Server version 1.0.0 on npm (mcp-dyson-appliances)
- Three environment variables documented (2 required, 1 optional country code)
What problem does it solve?
You want agent-driven automation against real hardware but lack a small, testable IoT MCP you can run locally with your own devices.
Who is it for?
Solo builders with Dyson devices who demo IoT integrations or automate a home office from their agent toolchain.
Skip if: Builders without Dyson hardware, teams that forbid storing appliance passwords in local env, or those needing enterprise facility management.
What do I get? / Deliverables
Your agent can issue Dyson purifier and fan commands over stdio MCP after you set account environment variables.
- Agent-invokable control of Dyson purifiers and fans
- Working reference for authenticated IoT MCP patterns
- Documented env-based setup for local stdio clients
Recommended MCP Servers
Journey fit
Hardware and account-backed APIs are integrated during Build when you wire real devices into agent workflows or side projects. Integrations subphase matches authenticated Dyson cloud control (email, password, country) exposed as MCP tools for agents.
How it compares
Consumer appliance IoT MCP, not a cloud deploy or monitoring platform.
Common Questions / FAQ
Who is mcp-dyson-appliances for?
Developers who own Dyson purifiers or fans and want Claude Code, Cursor, or similar agents to control them via MCP.
When should I use mcp-dyson-appliances?
Use it during Build when prototyping smart-home automations, integration patterns, or personal workflows tied to Dyson cloud control.
How do I add mcp-dyson-appliances to my agent?
Set DYSON_EMAIL and DYSON_PASSWORD (and optional DYSON_COUNTRY), install npm mcp-dyson-appliances v1.0.0, and register the stdio MCP server in your client config.