Amazon is rolling out a preview AI update for Alexa Plus that lets the assistant handle intricate smart-home commands across a wider roster of third-party devices. The change centers on automatic request routing and a new developer toolkit that lowers the barrier for manufacturers to expose unique capabilities.
Supported brands now include Bosch, Delta, Ecovacs, iRobot, Yale Home, Whirlpool, Tapo and Eufy. Device makers can surface specialized functions that earlier Alexa versions could not address, such as proprietary wash cycles or security-lock states.
In one demonstration, a user tells Alexa Plus that a child’s soccer jersey needs a deep clean yet must remain on cold wash. The assistant interprets the constraint, navigates the washer’s cycle menu and selects the appropriate setting without further prompts.
The update rests on Amazon’s AI developer toolkit and adoption of the Model Context Protocol, an open standard that lets AI models discover and invoke external tools. MCP is intended to accelerate onboarding for both hardware and software partners beyond the initial set of services.
Alexa Plus itself reached wide availability in February with native support for multi-step requests and voice-driven routine creation. At launch, however, it was restricted to a narrow list of third-party endpoints including Ticketmaster, OpenTable, Uber, Thumbtack, Expedia, Yelp, Square and Angi.
By adding MCP, Amazon is signaling that future growth will come from ecosystem breadth rather than solely from first-party services. Smart-home control remains the clearest near-term beneficiary because device heterogeneity has long fragmented user experience.
For hardware manufacturers, the toolkit offers a standardized path to expose differentiated features without building separate Alexa skills. Early movers such as iRobot and Yale Home can now surface capabilities that previously required custom integrations or were simply unavailable.
Commercially, the strategy tightens Amazon’s position in the post-purchase smart-home layer. Deeper device connectivity increases daily interaction frequency and raises switching costs for households already invested in Alexa routines.
Investors and competing platforms will watch whether MCP becomes a de-facto integration layer or remains Amazon-specific. If other assistants adopt the same protocol, device makers could face lower integration costs across the board.
The immediate test is whether the preview delivers reliable routing across the newly added brands without increasing latency or error rates. Success here would validate Amazon’s bet that an open tool protocol plus a capable language model can finally tame the fragmented smart-home market.