Tuya MCP for AI. Control every smart device with plain conversation.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
Tuya MCP Server controls and monitors your smart home or industrial hardware through natural conversation. It lets you query device status—checking if a sensor is online, finding its category, or getting its local key—and sends real-time commands (like toggling lights or adjusting temperatures) using only text prompts.
Stop jumping between apps; manage all connected Tuya devices from your AI client.
What AI agents can do with Tuya Automation
Get device
Queries and returns the detailed metadata for a specified Tuya device ID, including status, category, and local key.
Send commands
Sends direct control instructions to a connected Tuya device, such as toggling an LED or adjusting a switch state.
The server retrieves detailed information on a specified device ID, including its online status, hardware category, and local integration key.
The server sends specific instructions to the target Tuya hardware, such as turning lights on/off or setting operational modes.
You check if a device is currently online and reporting its heartbeat status within the Tuya Cloud.
Ask an AI about this
Waiting for input…
What AI agents can do with Tuya: 2 Tools for Device Control
These tools allow your agent to read the metadata of devices using get_device, and issue actionable control signals with send_commands.
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 Tuya on VinkiusGet Device
Queries and returns the detailed metadata for a specified Tuya device ID, including status, category, and local key.
Send Commands
Sends direct control instructions to a connected Tuya device, such as toggling an...
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.
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 Tuya, 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 Tuya. 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 2 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Managing your home infrastructure shouldn't feel like juggling five different apps., Solved with Vinkius AI Gateway
Right now, if you need to check the status of a smart plug, then adjust a dimmer switch, and finally verify a sensor reading, you open three separate mobile applications. You jump from the lighting app to the climate dashboard, copy one ID, and then cross-reference data in a maintenance portal. It's slow, tedious, and frustrating.
With this MCP server, your AI acts as the single pane of glass. Instead of opening apps, you just talk. 'Check the status on Zone A and set the bedroom lights to 30 percent.' The agent handles all those API calls—status check via `get_device`, command execution via `send_commands`—and gives you one clean answer.
Tuya MCP Server: Get full device control from chat.
The manual steps that disappear are the constant credential swapping and app navigation. You don't need to log into your developer portal just to see if a sensor is reachable, nor do you need to construct complex JSON payloads for simple toggles.
You simply tell your AI client what you want done. The system handles the protocol complexity under the hood. It’s instant control without the technical friction.
What your AI can actually do with this
You're sick of jumping between a dozen apps just to run your place? This server lets your AI client talk straight to your actual hardware, giving you a centralized control panel for everything connected via Tuya. It handles everything from simple switches to complex industrial sensors using only plain text conversation.
When you need to know what's going on with any device, you use get_device. This function queries and pulls detailed metadata based on a specific Tuya device ID. You get the full picture: its current online status, which hardware category it falls under, and even the local integration key—stuff you need for deep debugging or advanced setup.
To check if a device is actually running right now, get_device confirms its heartbeat status within the Tuya Cloud. It tells you instantly if that sensor or light fixture is reachable and functioning properly through your cloud project.
When it's time to take action, you use send_commands. This sends direct instructions to any connected Tuya device. You can tell your agent to toggle switches on and off, adjust brightness levels, or change the operational mode for specific hardware. It executes precise control commands directly to the target device.
Basically, if it's a smart device—whether it's running in your living room or out on an industrial site—your AI client uses these tools to manage it with just words.
019ea60c-e785-73aa-bac6-e5394ad56763 Here's how it actually works
The bottom line is that your AI client acts as a single point of access, translating simple text commands into complex hardware instructions.
Subscribe to the server and provide your required credentials: the Tuya Client ID, Secret, and Endpoint.
Your AI client initiates a request by asking a question or giving an instruction (e.g., 'Turn off the kitchen lights').
The agent calls get_device for status checks or send_commands to perform actions, returning confirmation of success or failure.
Who is this actually for?
This is for the ops engineer who's tired of clicking through five different dashboards just to check if three things are working. It’s built for facility managers and developers who need immediate, hands-free control over distributed hardware.
Monitors and controls hardware across multiple buildings or zones by simply asking the agent about status or issuing commands.
Quickly uses get_device to inspect device categories, local keys, and metadata while debugging new integrations.
Manages complex automation setups—like turning off all non-essential lights at night—using simple text prompts instead of building elaborate flows.
What Changes When You Connect
Centralized Control: Instead of opening a dozen apps, your AI client handles all hardware interactions. You query status or send commands directly from the chat window.
Deep Diagnostics: Use get_device to retrieve more than just an 'online' status. You get category details and local keys—essential info for advanced troubleshooting.
Real-Time Action: The send_commands tool lets you toggle switches, adjust brightness, or change modes instantly based on a simple text instruction.
Eliminates Context Switching: Stop jumping between your smart home app, your maintenance dashboard, and your terminal. Everything is unified in one conversation flow.
Industry Ready: Works for both residential smart homes (lights, plugs) and professional industrial setups (sensors, relays), making it versatile for any facility.
See it in action
The Quick Night Check
A resident leaves the house late. Instead of checking three different physical switches in the app, they ask their agent: 'Are all the main lights off?' The agent calls get_device for multiple IDs and confirms status across the entire home.
Debugging a Sensor
An IoT developer finds a sensor giving bad data. They use get_device to pull the device's local key and category metadata, which they immediately need for writing custom integration code—all without leaving their IDE.
Emergency Shutdown
A facility manager notices a leak alarm is active. They don't have time to navigate the main control panel. They tell the agent: 'Shut down power to Zone B.' The agent executes send_commands on all relevant relays.
Verifying Device Availability
Before running a major automation script, an engineer needs confirmation that 50 peripheral sensors are online. They ask the agent: 'Check connectivity for all Zone 3 devices.' The agent runs status checks to give them a clear pass/fail report.
The honest tradeoffs
Assuming Status
Thinking that just because you know the light should be on, it means it is. You might try to send commands without first knowing if the device ID is correct or online.
Always run get_device first with the suspected ID. This confirms the current status and validates the metadata before attempting a command using send_commands.
Overloading Commands
Trying to send three different commands (on/off, brightness change, mode set) in a single prompt when they belong to separate device groups.
Break it down. First, check the status of all components using get_device. Then, issue targeted instructions sequentially: 'Set brightness on Device X to 50 percent,' then 'Turn off Device Y.'
Ignoring Credentials
Trying to use the tool in a development environment without providing the correct Tuya Client ID and Secret.
The server requires your credentials upfront. Make sure you follow the setup steps: provide valid IDs, Secrets, and Endpoints before any tools will execute.
When It Fits, When It Doesn't
Use this server if your primary need is controlling or checking the physical state of proprietary IoT hardware (like lights, plugs, HVAC). The get_device tool lets you read status; send_commands lets you write actions. Don't use it if you just need to send a message between people—that requires a messaging service. Also, don't use it for database tasks like 'create a new user record'; those require different CRUD-type tools. This is purely about hardware interaction and device monitoring.
Questions you might have
How can I check if a specific smart device is currently online? +
Use the get_device tool with the target Device ID. The agent will return the current connectivity status along with other technical metadata from the Tuya Cloud.
Can I send multiple commands to a device at once? +
Yes! The send_commands tool accepts an array of command objects. You can trigger multiple actions, such as turning on a light and setting its color, in a single request.
What kind of technical details does the agent provide for my hardware? +
By running get_device, the agent retrieves the device category, its unique local key, the product name, and its current operational status, allowing for deep technical auditing.
What credentials does the agent need to use `send_commands`? +
It requires your Tuya Client ID, Secret, and Endpoint. You must provide these three pieces of information when setting up the server connection on Vinkius.
If a command fails after using `send_commands`, how do I troubleshoot it? +
The agent returns the specific error code provided by the Tuya Cloud API. You need to cross-reference that code with your hardware documentation to fix the issue.
When running `get_device`, what exactly is a 'local key'? +
The local key is a unique identifier for the device, specific to its physical setup. Developers use this detailed data point when building integrations that bypass standard cloud calls.
Does `send_commands` support every type of Tuya hardware? +
It supports commands defined by standard instruction sets (like toggling or setting brightness). For specialized or custom functions, you must consult the specific documentation for that device model.
Can I check connectivity status for devices outside my main Tuya account? +
No. This server is restricted to your connected Tuya IoT ecosystem only. Monitoring other hardware brands requires linking a different, dedicated integration service.
We've already built the connector for Tuya. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 2 tools are live and waiting.
You're up and running in seconds.
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.