# \[MCP\] Homey Developer MCP: give your agent direct access to crash reports, diagnostic reports and builds

**URL:** <https://community.homey.app/t/mcp-homey-developer-mcp-give-your-agent-direct-access-to-crash-reports-diagnostic-reports-and-builds/162116>\
**Category:** Developers\
**Created:** [November 12, 2026, 1:19am UTC](https://community.homey.app/t/mcp-homey-developer-mcp-give-your-agent-direct-access-to-crash-reports-diagnostic-reports-and-builds/162116 "2026-11-12T01:19:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![lucasvdh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lucasvdh/32/54915_2.png) [@lucasvdh](https://community.homey.app/u/lucasvdh)\
**Post date:** [November 12, 2026, 1:19am UTC](https://community.homey.app/t/mcp-homey-developer-mcp-give-your-agent-direct-access-to-crash-reports-diagnostic-reports-and-builds/162116/1 "2026-11-12T01:19:40Z")

</div>

Hi everyone!

I’ve built an MCP server for Homey app developers: **Homey Developer MCP**. It gives your agent (Claude Code, Claude Desktop, Cursor, VS Code or any other MCP client) access to the crashes, diagnostic reports, builds and install stats of your own Homey apps.

> **[Homey Developer MCP](https://lucasvdh.github.io/homey-developer-mcp/)**
>
> An MCP server for Homey app developers: crashes, diagnostic reports, builds and install stats of your own apps, right in your AI assistant.

## Why

When a user sends a diagnostic report or your crash count goes up, you open the developer tools site, click into a build, scroll through the stack traces, then do the same for the previous build. With this server you ask your agent instead, and it reads the crashes and reports itself, next to your code.

That shortens the feedback loop from a user’s report to a fix: in one session the agent reads the report, finds the line in your code, fixes it and can release the new build to test.

A few things it does that the developer tools site doesn’t:

- **Diagnostic reports, split up.** Reports users send with _Create diagnostics report_ end up between your crashes. The server picks them out and splits them into Log ID, the user’s message, stdout and stderr.
- **Crashes grouped per bug.** Homey counts an error that mentions a device id separately for every device. The server merges those by error message and the line in your own code, so you see which bug actually causes the most crashes.
- **Across builds.** Reports and crashes are stored per build. The server searches your newest builds at once.

## Things you can ask

- Which crashes happen most, and where in my code?
- What do this week’s diagnostic reports say? Do any share a cause?
- Did crashes go down after build 41?
- Is my latest build through processing? What did the reviewer say?
- Release build 42 to test and submit it for certification.

## Releasing and submitting builds

Off by default. With `HOMEY_MCP_ALLOW_WRITE=1` you get three extra tools: release a build to test or live, submit it for certification, and retract a submission. Athom only accepts live for a build that passed review, and clients that support it ask for confirmation before each call.

## Install

You need Node.js 18+ and your Personal Access Token from [Homey Developer Tools](https://tools.developer.homey.app/me). For Claude Code:

```
claude mcp add homey-developer --env HOMEY_PAT=pat-... -- npx -y homey-developer-mcp

```

Configs for Claude Desktop, Cursor and VS Code are on the website.

## Good to know

- Diagnostic reports contain your users’ messages and logs, including device names. The tools pass them to the agent you connect, so only use one you’re comfortable sharing that with.
- For push notifications when a build gets through review, use the flow triggers of my Homey app [App Insights for Developers](https://community.homey.app/t/app-pro-app-insights-for-developers-monitor-your-homey-apps/154747). The MCP server can only answer when it’s asked.
- It’s open source (GPL-3.0): [GitHub - lucasvdh/homey-developer-mcp: MCP server for Homey app developers: crashes, diagnostic reports, builds and install stats of your own apps · GitHub](https://github.com/lucasvdh/homey-developer-mcp)
- This is an independent community project and is not affiliated with Athom.

Questions, issues and ideas for more tools are welcome here or on GitHub.
