Homey Developer MCP
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Homey Developer MCP
An MCP server for Homey app developers. It gives an AI assistant access to the crashes, diagnostic reports, builds and install stats of your own Homey apps through Athom's apps API, and optionally lets it release builds and submit them for certification.
Tools
Tool | What it returns |
| Your apps and those of your Developer Organizations: live/test version, installs, crash counts |
| Builds of an app, newest first |
| Crashes and unhandled rejections of the newest builds, grouped by error and app file/line, most frequent first |
| Reports users submitted with Create diagnostics report, with their message and a stderr preview |
| One report in full: user message, stdout and stderr |
| Daily installs, optionally per driver |
| State of a build, why processing failed, reviewer comments and Athom's AI review |
Write tools
Only available when HOMEY_MCP_ALLOW_WRITE=1 is set; without it the client doesn't see them at all.
Tool | What it does |
| Puts a build on the |
| Sends a build to Athom for review. |
| Withdraws a build from review |
They are marked as destructive, so clients that support it ask for confirmation before each call. The server never replies to users or changes app settings.
Waiting for a build
An MCP server can't notify you by itself. To wait for a build in Claude Code, have it call get_build_status periodically, for example with /loop. That only runs while the session is open. For notifications on your phone, use the flow triggers of App Insights for Developers, such as The state of the test build has changed and The test build was approved.
How crashes and reports are told apart
Athom returns crashes, unhandled rejections and user-submitted diagnostic reports from the same endpoint (/app/{appId}/build/{buildId}/crash), all in the stack field. This server classifies them by their opening line and splits diagnostic reports into Log ID, user message, stdout and stderr.
Homey groups crashes by their exact stack, so an error that mentions a device id gets a separate group per device. get_crashes regroups by error message (with ids replaced by <id>) and the first stack frame in your app's own code, so the counts add up per actual bug.
A report or crash is stored on the build the user was running. The tools look at the newest 5 builds by default; pass builds or buildId to look further back.
Website: lucasvdh.github.io/homey-developer-mcp
Related MCP server: io.github.gjeltep/app-store-connect-mcp
Background
How this server came about, what it is based on and why it works the way it does: docs/background.md. What it uses of Athom's apps API, including the format of crash entries and diagnostic reports: docs/apps-api.md.
Setup
You need your Personal Access Token (it starts with pat-). You'll find it on tools.developer.homey.app/me, in the Personal Access Token section. Requires Node.js 18 or newer.
Claude Code
claude mcp add homey-developer --env HOMEY_PAT=pat-... -- npx -y homey-developer-mcpAdd --env HOMEY_MCP_ALLOW_WRITE=1 to enable the write tools.
Claude Desktop, Cursor and other clients
{
"mcpServers": {
"homey-developer": {
"command": "npx",
"args": ["-y", "homey-developer-mcp"],
"env": { "HOMEY_PAT": "pat-..." }
}
}
}Add "HOMEY_MCP_ALLOW_WRITE": "1" to env to enable the write tools.
Privacy
Diagnostic reports contain what your users wrote and the logs of your app on their Homey, including device names. With this server, that content reaches the AI assistant you connect it to. Only connect it to an assistant you're comfortable sharing that data with.
Development
npm install
npm testTo try a local build in Claude Code: claude mcp add homey-developer --env HOMEY_PAT=pat-... -- node /path/to/homey-developer-mcp/dist/index.js.
src/AthomApi.ts is copied from App Insights for Developers (lib/AthomApi.ts).
License
GPL-3.0
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Lets AI agents analyze API metrics, request logs, and traces, and manage apps and alerts.
Query your app's logs, metrics and incidents from your AI assistant.
Deploy apps from GitHub, read build/runtime logs, and manage your app's users from your AI agent.
Run your Krtuworks apps from an AI agent: setup, remote config, stats, players, bug reports.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Apple App Store Connect resources like apps, builds, TestFlight, and reviews through natural language.2014 npmMIT
- AlicenseCqualityDmaintenanceEnables management of App Store Connect resources including app reviews, TestFlight crashes, analytics reports, and Xcode Cloud workflows through natural language or AI agents.401MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to control a Homey Pro smart home hub, create automation flows from natural language, and query device and energy history.3621 npmMIT
- AlicenseAqualityCmaintenanceProvides AI assistants direct access to Apple's App Store Connect API, enabling them to manage apps, provisioning data, TestFlight builds, and App Store versions, including creating versions, attaching builds, and submitting for review.14MIT