SmartThings MCP for AI. Central control for every smart device in your home or office.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
How this MCP server connects to your AI agent
SmartThings MCP Server connects your entire smart home or office system directly to your AI agent. You manage devices, read real-time status reports (like temperature or lock status), and trigger complex automations—all through natural conversation.
It's your central control panel for every connected piece of hardware.
What AI agents can do with SmartThings Automation
List apps
Retrieves a list of all available SmartApps that can be installed on the system.
Create room
Adds a new, structured room division into an existing SmartThings location.
Execute device command
Sends immediate commands (on/off, set level) to any specific connected device.
Retrieves the current operational state, including attributes like temperature or switch on/off status, for any connected hardware.
Forces a specific action on a single device, such as turning it on, off, or setting its brightness level.
Triggers multiple predefined actions (like 'Movie Night') simultaneously using one command call.
Lists all connected hardware, locations, or rooms, allowing you to see the full scope of your installed IoT network.
Handles event subscriptions for SmartApps, which is key for building advanced, custom automation workflows.
Ask an AI about this
Waiting for input…
What AI agents can do with SmartThings MCP Server: 13 Tools for IoT Automation
These tools give your AI agent direct access to every function needed to monitor, command, and organize an entire smart home or office network.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using SmartThings on VinkiusList Apps
Retrieves a list of all available SmartApps that can be installed on the system.
Create Room
Adds a new, structured room division into an existing SmartThings location.
Execute Device Command
Sends immediate commands (on/off, set level) to any specific connected device.
Get Device Status
Checks the current operational state and attribute values of all connected...
List Devices
Lists every single hardware device currently connected to your account.
Execute Scene
Runs a pre-configured automation scene that controls multiple devices at once.
Get Device
Retrieves detailed metadata for one specific SmartThings device using its identifier.
Get Location
Gets detailed information about a specific geographical or logical area within your...
List Installed Apps
Shows all instances of SmartApps that are actually installed and running on the...
List Locations
Lists every primary geographical area or location accessible by your token (e.g....
List Rooms
Retrieves a list of all defined rooms within a specific SmartThings location.
List Scenes
Lists all the pre-configured, multi-device automation scenes available for execution.
List Subscriptions
Manages and views event subscriptions for advanced SmartApps workflows.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The SmartThings integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with SmartThings, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by SmartThings. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 13 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Manually checking your home or office system shouldn't require jumping between five different apps., Solved with Vinkius AI Gateway
Today, if you want to know the status of your smart devices—say, confirming that all lights are off before leaving for the day—you open the light app. Then you jump to the lock app. Then maybe a separate thermostat dashboard. You toggle through settings and screens until you finally confirm everything is running correctly. It's clicking through dashboards at 2 AM.
With this MCP server, your AI client handles it all in one go. You just ask, 'Are we secured?' The agent runs the necessary checks—calling `get_device_status` for locks and lights—and gives you a single answer: Green across the board. It's instant.
SmartThings MCP Server: Centralize control over every smart device.
Gone are the days of manually running routines. You no longer have to open the app, select 'Movie Night,' and hit play. The agent executes the complex sequence using `execute_scene` based on your prompt alone.
The difference is that you're dealing with a single conversational interface that understands device relationships. It doesn't just send commands; it manages your entire living space.
What your AI can actually do with this
You're connecting your entire smart home or office setup straight through this server, giving your AI agent total control over every piece of hardware. Forget talking to five different apps; you manage everything from one conversation. This system lets your AI client read real-time status reports and run complex automations across all your connected devices.
When you need to set up the physical structure, you start by knowing what space you're dealing with. You can call list_locations to see every main area accessible—things like 'Home' or maybe 'Office Wing A.' If you want granular detail on a specific spot, use get_location to pull all the data about that place.
Within those locations, you'll find defined rooms; you can run list_rooms to see what divisions exist, or if your layout changed and needs updating, you can call create_room to add a new structure.
To take stock of everything connected, use the inventory tools. You can list every single piece of hardware—lights, thermostats, locks, whatever it is—by running list_devices. If you need deep specs on just one item, like checking the model number or manufacturer for a specific unit ID, get_device pulls all that metadata for you.
This lets your agent build a full picture of what's actually installed.
Once you know what you got, you gotta check if it works. You don't want to assume the light is off; you need proof. Running get_device_status checks the current operational state and all attributes across every component in your location—it tells you if that switch is really toggled off or if the temperature sensor actually reads 72 degrees.
If you only care about one specific thing, checking a single unit's status is quick; running get_device_status gives you the whole neighborhood report.
The action commands are where things get real. You can force an immediate change to any device by executing a command using execute_device_command. This lets your agent toggle switches, dim lights to 30%, or adjust the thermostat without needing a specific routine—it's just raw control. For bigger jobs, you don't want to send fifty commands; instead, use execute_scene to run a whole pre-configured automation scene.
Think 'Movie Night' or 'Leaving Home'—one call runs multiple devices simultaneously.
For managing the underlying software that makes this stuff smart, your agent handles apps and workflows. You can see what SmartApps are available by calling list_apps. If you want to know which ones are actually running on your system, use list_installed_apps to see those instances. For advanced customization, you manage event subscriptions using list_subscriptions, which is key for building complex, custom triggers for the smart apps.
Finally, if your automation needs deep integration across multiple devices or services, you'll need to know how they connect. You can check the full scope of available SmartApps with list_apps and confirm what’s already running with list_installed_apps. The tools give you everything from listing every single connected device via list_devices, getting specific details on one unit using get_device, checking if a room exists with list_rooms or creating it with create_room, to triggering an instant, complex routine via execute_scene.
You'll never run out of control options.
019ea607-8b3b-72cc-a492-f3999bfa7dde 
Here's how it actually works
The bottom line is that you never have to open another app; your AI client does everything through one conversational interface.
Subscribe to the server and provide your SmartThings Personal Access Token (PAT).
Your AI client uses the token to connect to the MCP endpoint.
You give a conversational command (e.g., 'Turn off all lights in the kitchen'). The agent translates this into specific tool calls, executes them against the API, and reports the final status.
Who is this actually for?
Facility managers who hate manually checking building systems. Home automation enthusiasts tired of using ten different manufacturer apps. Developers testing complex IoT logic flows. If you manage more than three types of smart devices, you need this.
Automates the monitoring and shutdown of large office spaces by checking every room's temperature or locking down specific zones with simple queries.
Builds complex, multi-step routines (like 'Leaving Home') that require coordinating lights, locks, and thermostats across various brands from one interface.
Tests the full lifecycle of device states—from listing all devices to executing targeted commands—directly within their coding environment.
What Changes When You Connect
Eliminate app switching. Instead of opening the light app, then the thermostat app, and then the lock app to run a routine, running execute_scene handles all those steps with one command. The agent does the heavy lifting for you.
Get real-time status checks. You don't have to guess if something is working. Calling get_device_status confirms the current state of every component—battery life, temperature, switch position—before you act.
Structure your inventory logically. Use list_locations and create_room to map out your entire physical environment within the system. This structure makes it easier for the AI to target commands correctly.
Control complex routines easily. The server allows listing (list_scenes) and executing (execute_scene) multi-device workflows, meaning you can trigger 'Good Morning' or 'Vacation Mode' with a single prompt.
See everything connected. Use list_devices to pull up an exhaustive inventory of every hardware piece on the network. It’s your complete device manifest in one query.
See it in action
Troubleshooting a locked system
A facility manager notices the building temperature seems off. Instead of manually checking multiple dashboard panels, they ask their agent to 'Check the status of all HVAC components in the West Wing.' The agent calls get_device_status across multiple devices, quickly identifying that only the main thermostat component is reporting data.
Setting up a new zone
An owner adds a new entertainment center to their living room. They use the agent's ability to 'Create a dedicated media hub space.' The system calls create_room and then lists that new location using list_rooms, ensuring all future commands can target the right area.
Running a complex routine
It's time to leave for the day. Instead of manually setting five different devices, they tell their agent, 'Run the Away Scene.' The server executes execute_scene, which simultaneously locks doors, turns off lights, and lowers the thermostat.
Auditing installed features
A developer needs to know what automation capabilities are available. They use list_apps to see all possible SmartApps and then call list_subscriptions to verify which event handlers are currently active, ensuring their custom logic is hooked up correctly.
The honest tradeoffs
Assuming a command works
Telling the agent 'Turn off all lights' without verifying if those lights actually exist or are powered on.
First, call list_devices to confirm device existence. Then, use get_device_status to verify component power before running execute_device_command. This prevents silent failures.
Missing context when listing
Calling 'List my rooms' when the system needs to know which main location you mean, leading to vague or incomplete results.
Always call list_locations first. Then specify the exact location ID before calling list_rooms so the agent knows exactly where it should be looking.
Over-relying on single tools
Trying to manage a 'Movie Night' routine just by issuing separate commands for lights, TV, and blinds. This is slow and error-prone.
Use the list_scenes tool first. If the desired sequence exists, execute it with one call using execute_scene. That’s faster and more reliable.
When It Fits, When It Doesn't
Use this server if your goal requires centralized control over multiple physical devices—checking status, running commands, or executing complex routines across different brands (e.g., 'Check the temperature on Device A and turn off Light B'). You need it when managing a true IoT ecosystem.
Don't use it if you just need to read simple data that doesn't involve device state change (like checking weather forecasts, which might be handled by a dedicated weather API). Also, don't rely on it for pure scheduling; while scenes can automate, setting up recurring schedules is often better handled by the platform's native calendar or scheduler type tool instead of relying solely on execute_scene.
It's essential if you need to orchestrate actions across devices listed via list_devices, because that proves connectivity and capability. If you only need a single, isolated function (like just fetching a user profile), this server is overkill.
Questions you might have
How do I list all my smart devices using the SmartThings MCP Server? +
Call list_devices. This tool pulls up a complete manifest, giving you IDs and names for every single piece of hardware connected to your account.
Can I check if a device is actually powered on with get_device_status? +
Yes. get_device_status checks the live attribute values, so you can verify things like temperature readings or whether a component's power switch is reported as 'on' or 'off'.
What should I use to run my automated routines? +
You use execute_scene. This tool runs pre-defined, multi-step workflows. If you have a routine like 'Good Night,' it executes that whole sequence in one call.
Does SmartThings MCP Server let me organize my rooms? +
Yes. You can use list_locations to see your main areas, and then use tools like list_rooms or create_room to structure the physical space for better targeting.
How do I get detailed metadata about a specific device using the `get_device` tool? +
The get_device tool returns comprehensive data beyond just status. It provides model identifiers, hardware specs, and unique attributes necessary for advanced scripting or debugging your environment.
What is the difference between listing locations and rooms using `list_locations` vs. `list_rooms`? +
list_locations gives you the highest-level containers—like 'Home' or 'Office Floor'. You must use list_rooms after that to narrow down and see specific room subdivisions within a location.
How does the `list_subscriptions` tool help with complex automation workflows? +
It manages event subscriptions. Instead of just running a preset scene, you use this tool to listen for specific real-time events (like 'motion detected') and trigger actions based on that live data stream.
What is required to start using the SmartThings MCP Server after I subscribe? +
You need a SmartThings Personal Access Token (PAT). This token authenticates your agent's connection, giving it secure permission to control and monitor your specific smart home devices.
Can I check if my lights are on and see the current brightness level? +
Yes. Use the get_device_status tool with the specific Device ID. It will return the current state of all components, including switch status and level attributes.
How do I trigger a 'Movie Night' scene that I already created in the SmartThings app? +
First, use list_scenes to find the ID of your 'Movie Night' scene. Then, use the execute_scene tool with that ID to trigger all associated actions at once.
Is it possible to organize my devices into a new room using this server? +
Yes. You can use the create_room tool by providing the target Location ID and the desired name for the new room subdivision.
We've already built the connector for SmartThings. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 13 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.