Smart home MCP server for connected devices
Connect supported lights, speakers and vacuums to your AI through Port OS cloud. See compatible devices, setup steps and alpha availability.
Control the devices you already own through Port OS cloud: Philips Hue lights, Sonos speakers, supported Roborock vacuums and other available integrations. Connect an MCP-compatible AI assistant, choose its access, and ask it to work with your devices.
Connect a device · Connect your AI · Try a simulator first
What a smart home MCP server does
The Model Context Protocol, or MCP, gives an AI application a standard way to use external tools. A smart home MCP server connects those tools to devices: the assistant can find an available light, check its state and request a supported change.
Port OS supplies the hosted server and the connections to supported device providers. You use a Port OS account and link your existing provider accounts. You do not need to run a Home Assistant instance to use Port OS. Some devices still need their manufacturer's bridge, account or cloud service.
For example, ask your assistant to find the living-room Hue light, check whether it is on, then turn it off. It should use the device's available controls and check a fresh reading afterward. A successful request alone does not prove that a physical light changed.
Devices and actions you can connect
The following are examples from the current alpha integrations. Individual devices expose their supported controls after connection; a brand name does not guarantee every model or action.
| Integration | Example tasks | What to check first |
|---|---|---|
| Philips Hue | Change supported lights, control rooms or zones, recall Hue scenes | Your Hue account, bridge and remote access; the lights and scenes returned by the connection |
| Sonos | Pause playback, adjust supported playback controls, work with native speaker groups | Account authorization, player capabilities and supported media sources |
| Roborock | Read supported vacuum state and request supported cleaning controls | Model support, account verification and the controls exposed by that device |
Browse available device integrations for the current choices. A waitlist entry means a connection is not ready to use. Shelly is currently a waitlist integration. Google Nest support is distinct from support for every device in a Google Home household.
Connect your home in three steps
1. Add a supported device provider
Open Add a Device, select your provider and follow its sign-in or verification steps. Then check Your Devices to confirm what Port OS discovered. Signing into Port OS does not automatically connect a manufacturer account.
If you want to learn the flow before connecting physical devices, follow the simulator quick start. A simulator demonstrates the software path; it does not test your home network or a manufacturer's service.
2. Connect an MCP-compatible assistant
Choose your client in Link to AI and use its maintained setup guide. The remote MCP endpoint is:
https://api.portoperatingsystem.com/mcpYour client must support the server's remote connection and authorization flow. Adding a URL is the start of setup; finish sign-in and review the requested access. The MCP connection guide explains the connection requirements.
3. Try one clear task and verify it
Start with a named device and a reversible action: “Find the desk light, tell me whether it is on, and turn it off.” Confirm the target before acting, then compare a fresh state reading with what you observe. If state is stale or unavailable, ask the assistant to say so instead of reporting success.
Once that works, explore the device's other supported actions. Natural-language requests depend on the assistant choosing the right tools as well as the underlying integration working.
Choose access you are comfortable granting
Reading device information and controlling devices are separate permissions. Review what the client requests and which resources it can use. The permissions guide explains how scopes and resource access work together.
Remove a client's access when you stop using it; see the token lifecycle guidance. Disconnecting an AI client and disconnecting a device provider are different actions. Review each connection you want to remove.
Availability, costs and limits
Port OS is in alpha. Available integrations, device coverage and setup requirements can change. Review the live integration catalog and contact us if you need pricing or compatibility confirmed before choosing it. Your assistant and device provider can have their own subscriptions, account requirements and service limits.
The hosted connection depends on internet access and the relevant provider services. MCP access by itself does not make an assistant run continuously, create a schedule or monitor your home in the background. Those tasks need an explicitly configured automation or event workflow.
Questions before you connect
Can I use devices that are not listed?
Check the catalog first. Port OS cannot control a device simply because it supports Wi-Fi, Matter or another smart-home standard. It needs an available integration that exposes the relevant device and action.
Why can the assistant see a device but not change it?
Check the client's control permissions, the specific device capabilities and its provider connection. A readable state is not a promise that every control is supported. If the provider requires a new sign-in, complete that first.
Should I use Port OS or Home Assistant?
Port OS fits a hosted connection to supported provider accounts. Home Assistant is worth considering when you want a home platform you run and manage, particularly for devices already connected there. Read Port OS versus Home Assistant MCP or compare local and cloud smart home MCP servers before choosing.
Where can I see the tools?
The MCP reference documents the tool interface. How the Port OS MCP integration works explains how an assistant finds device capabilities and requests an action.