{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-homey","slug":"homey","name":"Homey","type":"mcp","url":"https://github.com/pigmej/python-homey-mcp","page_url":"https://unfragile.ai/homey","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-homey__cap_0","uri":"capability://tool.use.integration.device.state.querying.and.control.via.mcp.protocol","name":"device state querying and control via mcp protocol","description":"Exposes Homey device objects through the Model Context Protocol (MCP), allowing LLM agents to query device capabilities, read current state (on/off, brightness, temperature, etc.), and send control commands. Implements MCP's resource and tool abstractions to map Homey's REST API device endpoints into standardized LLM-callable operations, with automatic schema generation for device-specific capabilities.","intents":["Query the current state of all smart home devices in natural language","Send control commands to specific devices (lights, switches, thermostats) from an LLM agent","Discover what capabilities each device supports without manual configuration","Build conditional logic in agents based on device state (e.g., 'if living room light is on')"],"best_for":["LLM agent developers building smart home automation workflows","Teams integrating Homey with Claude or other MCP-compatible AI models","Developers prototyping voice assistant integrations with Homey"],"limitations":["Latency depends on Homey hub network connectivity; local network required for reliable operation","Device state is eventually consistent — rapid successive queries may return stale state if Homey hub hasn't synced","No built-in caching layer; each query hits Homey REST API, adding ~100-500ms per request depending on hub load","Limited to device types and capabilities exposed by Homey's device driver ecosystem"],"requires":["Homey hub (hardware) with active network connection","Homey API credentials (app token or OAuth)","Python 3.8+","MCP client implementation (e.g., Claude Desktop with MCP support)"],"input_types":["natural language queries from LLM","structured tool calls with device ID and command parameters"],"output_types":["JSON device state objects","command execution confirmation","device capability schemas"],"categories":["tool-use-integration","smart-home-control"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-homey__cap_1","uri":"capability://automation.workflow.flow.execution.and.automation.triggering.via.mcp.tools","name":"flow execution and automation triggering via mcp tools","description":"Exposes Homey Flows (automation rules) as callable MCP tools, allowing LLM agents to trigger pre-configured automations by flow ID or name. Implements a tool registry that maps Homey flow objects to MCP tool definitions with parameters for flow arguments, enabling agents to orchestrate complex multi-step automations without directly controlling individual devices.","intents":["Trigger a pre-built Homey flow (e.g., 'movie mode' that dims lights and closes blinds) from an LLM agent","Execute conditional automations based on agent reasoning (e.g., 'if user is away, activate security flow')","Chain multiple flows together in an agent workflow","Allow users to define complex automations in Homey UI and invoke them via natural language through an LLM"],"best_for":["Non-technical users who want to control complex automations via voice/chat without learning agent programming","Developers building multi-step smart home workflows that benefit from Homey's visual flow editor","Teams where automation logic is maintained in Homey but triggered by external AI systems"],"limitations":["Flow execution is asynchronous; agent receives only acknowledgment, not real-time feedback on flow completion","No built-in flow parameter validation — malformed arguments fail silently or with generic Homey API errors","Flows must be pre-created in Homey UI; MCP cannot dynamically create or modify flows","Flow execution logs are not exposed through MCP; debugging requires checking Homey app directly"],"requires":["Homey hub with at least one configured Flow","Homey API credentials with flow execution permissions","Python 3.8+","MCP client with tool-calling support"],"input_types":["flow ID or name string","optional flow parameters as key-value pairs"],"output_types":["flow execution status (queued/started)","flow result or error message"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-homey__cap_2","uri":"capability://memory.knowledge.zone.aware.device.organization.and.context","name":"zone-aware device organization and context","description":"Organizes devices into Homey Zones (rooms/areas) and exposes zone membership through MCP resources, enabling agents to understand spatial context and issue zone-scoped commands (e.g., 'turn off all lights in the living room'). Implements zone hierarchy as queryable resources that map device IDs to zone names, allowing agents to reason about device location without explicit configuration.","intents":["Query which devices are in a specific room or zone","Issue commands to all devices in a zone (e.g., 'turn off all lights in bedroom')","Build location-aware agent logic (e.g., 'if motion detected in kitchen, turn on kitchen lights')","Provide spatial context to LLM for more natural responses (e.g., 'the living room has 3 lights and a thermostat')"],"best_for":["Developers building voice assistants that need to understand room context","Multi-room smart home setups where zone-scoped commands are more natural than device-by-device control","Agents that need to infer user intent from location (e.g., 'turn on lights' → infer which room based on context)"],"limitations":["Zone structure is static; changes in Homey UI are not reflected in real-time without reconnection","No hierarchical zone support (e.g., 'upstairs' containing 'bedroom' and 'bathroom'); zones are flat","Zone-scoped commands require agent to iterate over all devices in a zone; no native Homey API for zone-level bulk operations","Devices can only belong to one zone; cross-zone device groups are not supported"],"requires":["Homey hub with zones configured","Python 3.8+","MCP client"],"input_types":["zone name or ID string","device query filters"],"output_types":["list of devices in zone","zone metadata (name, icon, device count)"],"categories":["memory-knowledge","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-homey__cap_3","uri":"capability://data.processing.analysis.llm.optimized.context.and.schema.generation","name":"llm-optimized context and schema generation","description":"Automatically generates structured schemas and context representations for Homey devices, flows, and zones optimized for LLM consumption. Implements schema inference from Homey device capabilities and produces concise, LLM-friendly descriptions that reduce token usage and improve agent reasoning. Includes heuristics for generating natural language descriptions of device capabilities and constraints.","intents":["Reduce token overhead by providing compact, LLM-optimized device schemas instead of raw API responses","Enable agents to understand device capabilities without parsing verbose Homey API documentation","Generate natural language descriptions of devices and flows for inclusion in agent system prompts","Automatically infer device types and capabilities for better agent reasoning (e.g., 'this is a dimmable light')"],"best_for":["Developers optimizing token usage in LLM-based smart home agents","Teams building multi-model agents that need consistent schema representations across different LLMs","Builders who want to minimize prompt engineering by leveraging auto-generated context"],"limitations":["Schema generation is heuristic-based; edge-case device types may produce inaccurate or incomplete schemas","No customization hooks for schema generation; all devices follow the same template","Context generation is static; dynamic device state changes are not reflected in generated schemas","LLM-optimized descriptions are English-only; no multi-language support"],"requires":["Python 3.8+","Homey hub with devices/flows configured","MCP client"],"input_types":["Homey device/flow/zone objects"],"output_types":["JSON schema objects","natural language descriptions","capability summaries"],"categories":["data-processing-analysis","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-homey__cap_4","uri":"capability://tool.use.integration.mcp.resource.and.tool.registry.with.dynamic.capability.discovery","name":"mcp resource and tool registry with dynamic capability discovery","description":"Implements MCP's resource and tool abstractions to expose Homey devices, flows, and zones as discoverable resources and callable tools. Uses a registry pattern to dynamically map Homey objects to MCP definitions, enabling clients to discover available capabilities at runtime without hardcoded tool definitions. Supports both resource-based queries (read-only state) and tool-based actions (commands).","intents":["Allow MCP clients to discover all available Homey devices, flows, and zones at runtime","Expose device control as MCP tools with proper parameter schemas and descriptions","Enable clients to query device state as MCP resources without executing commands","Support dynamic capability discovery as new devices are added to Homey"],"best_for":["MCP client developers building Homey integrations","Teams using Claude Desktop or other MCP-compatible tools that need dynamic capability discovery","Developers who want to avoid hardcoding Homey device/flow definitions"],"limitations":["Dynamic discovery requires MCP client to re-query registry; no push-based notifications for new devices","Tool parameter schemas are generated from Homey API; complex or non-standard device parameters may not map cleanly to MCP schema","No built-in versioning or deprecation handling for tools; breaking changes in Homey API could break client integrations","Registry is in-memory; no persistence across MCP server restarts"],"requires":["Python 3.8+","Homey API credentials","MCP client implementation"],"input_types":["MCP resource/tool discovery requests"],"output_types":["MCP resource definitions","MCP tool definitions with schemas","capability lists"],"categories":["tool-use-integration","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-homey__cap_5","uri":"capability://tool.use.integration.homey.api.authentication.and.session.management","name":"homey api authentication and session management","description":"Handles Homey API authentication (OAuth or app token) and manages session lifecycle for MCP connections. Implements credential caching and refresh logic to maintain persistent connections to the Homey hub without requiring re-authentication between requests. Supports both local network and cloud API endpoints with automatic fallback.","intents":["Authenticate with Homey hub using stored credentials without user interaction","Maintain persistent authenticated sessions across multiple MCP tool calls","Handle token refresh automatically when credentials expire","Support both local network and cloud API access with transparent fallback"],"best_for":["Developers deploying Homey MCP servers that need to run unattended","Teams using Homey cloud API and requiring automatic credential refresh","Builders who want transparent authentication without managing tokens manually"],"limitations":["Credentials are stored in memory; no encryption at rest (requires external secret management for production)","No built-in support for multiple Homey hubs; single hub per MCP server instance","OAuth flow requires user interaction for initial setup; no headless OAuth support","Local network access requires hub and client to be on same network; no VPN/tunnel support"],"requires":["Homey API credentials (app token or OAuth client ID/secret)","Python 3.8+","Network access to Homey hub (local or cloud)"],"input_types":["API credentials (token or OAuth credentials)"],"output_types":["authenticated session","API response data"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":29,"verified":false,"data_access_risk":"high","permissions":["Homey hub (hardware) with active network connection","Homey API credentials (app token or OAuth)","Python 3.8+","MCP client implementation (e.g., Claude Desktop with MCP support)","Homey hub with at least one configured Flow","Homey API credentials with flow execution permissions","MCP client with tool-calling support","Homey hub with zones configured","MCP client","Homey hub with devices/flows configured"],"failure_modes":["Latency depends on Homey hub network connectivity; local network required for reliable operation","Device state is eventually consistent — rapid successive queries may return stale state if Homey hub hasn't synced","No built-in caching layer; each query hits Homey REST API, adding ~100-500ms per request depending on hub load","Limited to device types and capabilities exposed by Homey's device driver ecosystem","Flow execution is asynchronous; agent receives only acknowledgment, not real-time feedback on flow completion","No built-in flow parameter validation — malformed arguments fail silently or with generic Homey API errors","Flows must be pre-created in Homey UI; MCP cannot dynamically create or modify flows","Flow execution logs are not exposed through MCP; debugging requires checking Homey app directly","Zone structure is static; changes in Homey UI are not reflected in real-time without reconnection","No hierarchical zone support (e.g., 'upstairs' containing 'bedroom' and 'bathroom'); zones are flat","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.37,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:03.041Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=homey","compare_url":"https://unfragile.ai/compare?artifact=homey"}},"signature":"ONAYRKtS1SA1CaY0SNHueLIu1CheJtDsVzeV5Z3JbgqHwlRMq8a5NbmVQdwr+ngio3sijXFkaO45Eehd0cRXAA==","signedAt":"2026-06-22T05:37:38.050Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/homey","artifact":"https://unfragile.ai/homey","verify":"https://unfragile.ai/api/v1/verify?slug=homey","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}