{"id":"tuya-mcp-server","name":"tuya-mcp-server","homepage":"https://pypi.org/project/tuya-mcp-server/","repo_url":null,"category":"infrastructure","subcategories":[],"tags":["mcp","smart-home","tuya","automation","iot","agent-tools"],"what_it_does":"tuya-mcp-server is an MCP server that bridges an MCP-capable agent to Tuya/Smart-home style device control and data access (e.g., discovery and interacting with Tuya devices) using the Tuya integration backend it wraps.","use_cases":["Smart home automation assistants that need to read device states and control Tuya devices","Conversational troubleshooting for connected devices","Building agent workflows for routines (switching, brightness, sensors) using Tuya device APIs via MCP"],"not_for":["High-security unattended operations without safeguards","Mass data export/auditing pipelines where Tuya API rate limits are problematic"],"best_when":"You want an LLM agent to control/query Tuya devices via standardized MCP tool calling, and you can supply the necessary Tuya credentials/config to the server.","avoid_when":"You cannot tolerate the operational risk of controlling physical devices from an autonomous agent, or you lack clear rate-limit/error-handling behavior for your Tuya account.","alternatives":["Use Tuya’s official APIs (where available) directly with a REST integration","Use Home Assistant with a Tuya integration and connect the agent to Home Assistant tools instead of Tuya directly","Custom middleware wrapping Tuya APIs with your own auth, RBAC, and safety checks"],"af_score":42.5,"security_score":39.2,"reliability_score":26.2,"package_type":"mcp_server","discovery_source":["pypi"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:41:08.748356+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Tuya account authentication (typically via API credentials/client key/secret or an OAuth-like flow depending on the Tuya integration used)","MCP server configuration with Tuya credentials"],"oauth":false,"scopes":false,"notes":"Auth method details (exact Tuya auth flow, required credentials, and whether scopes/RBAC exist) are not provided in the supplied prompt, so the evaluation assumes configuration-based credential usage typical for Tuya integrations."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information was provided; assumes open-source/self-hosted with costs only from hosting and any Tuya API access requirements."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":42.5,"security_score":39.2,"reliability_score":26.2,"mcp_server_quality":70.0,"documentation_accuracy":50.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":45.0,"rate_limit_clarity":20.0,"tls_enforcement":50.0,"auth_strength":45.0,"scope_granularity":20.0,"dependency_hygiene":40.0,"secret_handling":40.0,"security_notes":"Security specifics (TLS enforcement, credential handling, logging/redaction, RBAC/scopes, and dependency health) are not included in the supplied prompt. For an MCP server that controls IoT devices, key risks are credential leakage via logs, insufficient authorization boundaries, and unsafe agent-driven actions without approval/sandboxing.","uptime_documented":0.0,"version_stability":45.0,"breaking_changes_history":20.0,"error_recovery":40.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Tool calls may be stateful and not naturally idempotent (e.g., toggles/switch commands)","Tuya device discovery and control can be sensitive to account permissions and network/API rate limits","Autonomous agents may repeatedly issue control commands unless rate limiting/safety guards are implemented above the MCP layer"]}}