Because capabilities are readable per device, an assistant can establish what a given device will accept before it sends anything — which is the difference between controlling a home and guessing at it.
A wrapper around Samsung's SmartThings public API. Devices, their current status and their capabilities are readable, and commands go the other way. Tools are discoverable before you supply a token, and the token is only validated when one is actually called.
- Every device on the account listed, and any one of them read in full
- Current status for a device — what it is doing right now, not what it was last set to
- The capability list for a device, which is what tells you which commands it will accept
- Commands sent to a device through that same capability model
- Locations and rooms listed, so devices can be reasoned about by where they are
Go 1.23 or newer to build. A SmartThings Personal Access Token from account.smartthings.com/tokens with the scopes you intend to use, supplied through the environment — the server starts without it for tool discovery, but every real operation needs it.
One command plus a key — npx -y @smithery/cli install @langowarny/smartthings-mcp --client claude, then supply credentials