[APP][Pro] MCP AI Bridge: talk to your Homey with Claude, ChatGPT, Gemini, Copilot, Cursor, Mistral, Ollama, LM Studio, n8n, Home Assistant or any AI, also from Telegram and WhatsApp

@weide43 now aim working since one week with your app, i made first the easy way over the local connection with Claude, its in the moment enough for me and i have all under control… meanwhile i bought the Pro Version because it makes so much fun! All the things which are not working with the original MCP works now, so happy :innocent:

What should i say, it feels like a new World and i cant stop working with it :slight_smile: , yesterday Claude build my first Dashboard, unbelievable the result, it takes about 10minutes and the result..it was insane…before i invest hours - days to build something like this and now…I am at a loss for words regarding this, thx for building this app, it. brings my smart home and homey on the next level!

Thx for providing & developing of this app, thx also to all people who are help to develop this app further, aim appreciate it!.. keep on rolling!

@Rammstein thanks, that’s great to read. Ten minutes for a dashboard is exactly what I hoped for when I built that part. If you run into something that doesn’t work the way you expect, or you miss something, post it here: most of the recent fixes started as a post in this topic. Enjoy building.

A short update on the last few versions. Most of it is about safety, and most of that you will never see, so here is what changed.

5.3.0 (live): a full audit of the whole app

I went through the whole app, every way in and out, and fixed everything that came up. The main theme: a key could sometimes do more through a side door than through the front door. Those doors are closed now.

  • Change plans, scheduled tasks, undo, OAuth approval and resources keep to the permission and tool selection of the key that started them. Before, a scheduled task or an approved plan could end up running with more rights than the key that made it.
  • A connector you approve with OAuth never gets more rights than the API key you approved it with.
  • Guardrails read a value the way Homey does: “off”, “0” or “no” no longer slip past a rule that is set on false.
  • Strict guardrails also check flows that are created, changed, restored or switched on.
  • A flow card that runs code counts as code, from any app, not only HomeyScript.
  • The dashboard turns away visitors that come in through a proxy or a tunnel, so a tunnel can no longer put it on the internet by accident. If you reached the dashboard that way, that stopped on purpose: it is meant for your own network.
  • Wrong keys are slowed down.
  • The settings page works with a screen reader, and its messages are in your own language.

5.4.2 (with Athom for review)

  • Export and import of the bridge settings, on the Security tab. One file with your settings, dashboards, scheduled tasks, home profile and skills. Keys and tokens stay out unless you confirm with a key that has full rights, and that is written to the security log. An import first shows what would change, and is applied all at once or not at all.
  • The AI memory can be kept per API key instead of shared by every assistant. Shared stays the default, so nothing changes unless you switch it.
  • The settings page follows your phone’s dark mode, and all thirteen tabs are in view at once instead of a row you had to swipe. The text at the top of the main tabs is shorter.
  • The dashboard takes its colours from one set, with better contrast for warnings in the light theme.

There is nothing you need to do: update when it reaches you. Every version is in post 3.

6.0 is on its way

Version 6.0 is uploaded and waiting for Athom’s review. It goes live by itself once it is approved; the test version has it already: https://homey.app/a/community.mcp-ai-bridge/test/

The biggest update so far. In short:

  • Voice messages and photos in Telegram and WhatsApp, and a camera picture back when you ask who is at the door.
  • A house log, and “what happened while I was away” in one answer, or /weg in Telegram.
  • An energy manager that plans the car, the boiler and the home battery around the prices, PV Forecast and your capacity peak. It starts in a trial mode that only shows what it would do.
  • A house watch and a wellbeing check, in your own language.
  • Flows in plain words: explained, tested, copied in bulk, and where every device is used.
  • A profile per Ask a model card, tools of other MCP servers, a chat with a microphone on the dashboard, and simple commands handled on the Homey without a model.

Two things to know when you update:

  • New keys are lean: short tool descriptions and compact answers, about half the tokens. An existing key stays as it was; you switch it on the Security tab, under Tools.
  • Every install now needs an API key. If you never set one, 6.0 makes one for you on its first start, so there is nothing to create yourself. Below is how to put it in your clients.

Getting the key into your clients

  1. Open the app’s settings: More, Apps, MCP AI Bridge, Configure app. The Status tab shows the new key in a box at the top. It is shown only there, so copy it and keep it somewhere safe.
  2. Leave that box open and go to the Connection tab. Pick your client: the wizard now writes the config with the key already in it. Paste it into your assistant and restart the assistant. Do this for every client you use (Claude Desktop, Claude Code, Cursor, n8n and so on).
  3. Press Got it on Status once all your clients have the key. From then on the key is no longer shown, and the wizard writes YOUR_API_KEY where the key goes.
  4. Missed the key, or want a separate key per assistant? On the Security tab, under API keys: give it a name, pick a permission and press Create key. That key is also shown once. In the wizard’s config, replace YOUR_API_KEY with it.

For fourteen days your clients keep working without the key, so nothing stops working on the day you update. During that time the Status tab lists the clients that still connect without a key, by address. After the fourteen days, a client without the key is refused. Need more time? The same box on Status has a button to extend once, by fourteen days.

The first post is rewritten for 6.0, with a section on Athom’s MCP server versus this one, and which assistant to pick.

A correction to #75 and #96. I wrote that only Business, Enterprise and Edu could write through a ChatGPT connector. That was wrong: as @J_Reeves showed in #77, Plus and Pro can create flows and switch devices once developer mode is on, and ChatGPT asks you to confirm every change. Sorry for the confusion.

@Mariomark1541, a late check on #92: after the 4.15.1 fix, did the “Ask a model a question” card show up in the Advanced Flow editor as well? In 6.0 every ask card also takes an optional profile, so if anything about those cards looks off, I would like to hear it.

@Laffen999, did refreshing the connector in ChatGPT’s web settings bring dashboard_update and dashboard_restore into the list (#148)? From 6.0 the Status tab shows per connector at which version it last fetched the tools, and says when one is behind.

That did the trick! Refreshing the connector through ChatGPT on my PC brought the missing tools back, and everything is working as expected now. Thank you so much for your help!

I also want to say how much I appreciate the work you’re putting into this app. It has genuinely transformed the way I develop and manage my smart home. Troubleshooting, fine-tuning automations, and implementing improvements have become dramatically faster and easier.

It’s amazing how much more I can accomplish with Homey and ChatGPT working together. Your app has made a huge difference, and I’m really excited to see how it continues to evolve.

Keep up the fantastic work, and thanks again for making this possible! :blush:

6.1 replaces 6.0 in the review

6.0 was still waiting for Athom’s review, so 6.1 takes its place: you get both in one update. The test version has it already: https://homey.app/a/community.mcp-ai-bridge/test/

Your assistant gets smarter with your home. Skills are ways of working your assistant reads before a bigger task. There were seven, now there are seventeen:

  • The energy manager: reading its plan, explaining it, the trial mode.
  • The house log and house watch: “what happened while we were away”, and setting up the wellbeing check with the consent of the person it watches.
  • Replacing a device: a new car or a new sensor, put in place everywhere the old one was used, with a plan you see first.
  • Looking after your flows: why a flow did or did not run, testing without switching the house, repairing and tidying.
  • Leaving home and holidays, notifications and lighting and moods.
  • Getting to know your home: a short first conversation, so later ones start with your names and house rules. Nothing is saved without your yes.
  • Devices that behave differently: cloud devices that react a few seconds later, chargers, lamps behind a plug.
  • Working efficiently: the right tool for each question, with fewer calls and tokens.

Every assistant also gets a few working rules when it connects: find a device instead of listing everything, read many states at once, and treat a refused call as a rule you set.

Fixed:

  • Editing a long Advanced Flow through an assistant could drop connections. Answers that are read to be sent back now always come back whole.
  • Undo did not remember switching a device, and a preview showed the old value as unknown.
  • On a lean key, a strict client such as Claude Code could refuse answers like the home briefing.

Everything else from the 6.0 announcement above still holds, including the API key on every install.

@Laffen999, good to hear the refresh brought the tools back, and thank you for the kind words. That is exactly what this app is for.

I am trying to get a correct API key for Gemini to setup ‘Model ask’. But I can’t get a ‘sk-…’ API key. Got the MCP AI and Gemini-CLI running and working. But I can’t seem to get any futher, so I can chat with Gemini.

MCP AI Bridge bug report

  • App version: 5.3.0
  • Homey: Homey Pro (2026) / firmware 13.5.3
  • Tools: 197, sessions: 0, schedules: 0, subscriptions: 0, broken flows: 0
  • Flow write: no PAT set (write disabled, reads only)
  • API key: none, scoped keys: 2, PAT: none, access mode: full
  • Blocked tools: devices_delete, flows_delete, advanced_flows_delete, zones_delete, alarms_delete, logic_delete, flow_folders_delete, apps_uninstall
  • IP whitelist: on, rate limit: 0, destructive limit: 0, webhooks: 0
  • Port: 52199, server: running
  • HTTPS: off

@Dricus, a Gemini key does not start with sk-. The “sk-…” in the key box was an example of an OpenAI key, and that sent you looking for the wrong thing. Sorry about that: the next version shows how each provider’s key begins.

For Ask a model with Gemini:

  1. Go to https://aistudio.google.com/apikey, sign in with your Google account and click Create API key. The key begins with AIza.
  2. In the app settings, open the Ask a model tab, switch on Let a flow ask a model a question and choose Google (Gemini) as the provider.
  3. Leave the model empty (it then uses gemini-flash-latest), paste the key and save.

The flow card Ask a model a question works from then on. To chat with your home from your phone, the Chat tab connects Telegram or WhatsApp to that same model.

A free key works. Do read the note that appears when you choose Gemini: without billing, Google may use your questions and answers to improve its products.

Gemini CLI is a separate route: it talks to the bridge with the bridge’s own API key (Security tab), not with a Google key. Since that already works for you, you can talk to your home in Gemini CLI right now.

Thanks for your answer. I am still a n00b regarding MCP. For me this is a way to learn more. Gonna check another AI.

6.1 and 6.2 are live

6.1 went live today, and 6.2 right after it, so an update now gives you both. On top of the seventeen skills from 6.1 in the post above, 6.2 brings:

Fewer tokens for lists. On a lean key, a list of devices now gives each device’s room by name, with each room’s id listed once underneath, instead of a long id on every row. A list of lights in three rooms got noticeably shorter, and your assistant still has the ids it needs to act on a room.

The right key example under Ask a model. The key box always said “sk-…”, which is how an OpenAI key begins. It now shows how the provider you chose starts its keys, so for Gemini you see “AIza…”. Thanks to @Dricus for the question that showed this.

Memory. Someone sent a diagnostic report on 12 November: the app ran out of memory and restarted about every half hour, even with nobody connected. I could not reproduce it here, so 6.2 does two things:

  • A live connection that stopped reading, such as a dashboard on a tablet that went to sleep, is now closed instead of filling the app’s memory.
  • The app writes a short line about its memory to its log. If it still happens, a new diagnostic report shows what grew, and I can fix the real cause.

If that report was yours, please send another one after updating to 6.2. Or reply here, so I know who to answer.

Hi Danny,

MCP AI Bridge v6.1.0 (test channel) on my Homey Pro keeps crashing with “Memory Warning Limit Reached” (exit code/signal unknown). Homey shows 5 crashes so far. The app restarts and runs normally again afterwards.

Diagnostic report wasn’t mine, but I had some problems today. I only saw a crash once. Claude noticed it 5 times.

Diagnostic report: a1195449-4a17-4516-906e-4a81b2ef8b29

Thanks for the great app!

I update to 6.2.0

Rudy

@RudolfT, thanks for the report, it helped. Your crashes are a different kind from the one in the report I mentioned above. There the app’s working memory filled up. With you, Homey stopped the app because everything it held together, pictures and other data outside that working memory included, went over the limit Homey sets for an app. Each time it came back by itself, as you saw.

What I cannot see yet is which part grows. So 6.2.1 is live now, and it writes a line about its memory to its log: after the first minute, every quarter hour, and more often as memory fills up. Since 6.2.1 that line also shows the memory outside the working memory, and the most the app has used so far.

If it crashes again on 6.2.1, please send one more diagnostic report. The log then shows what grew, and I can fix the real cause.

Two more things from your log:

  • Just before the first crash, Claude ran a few HomeyScripts that took more than ten seconds and were cut off. If you remember what they did, for example reading long lists or Insights, that helps narrow it down.
  • Every start logged “Action card mcp_agent_ask failed”. That was a false alarm: the card always worked. 6.2.1 no longer logs it.

I asked Claude what I was doing. I’ll send the answer in privat message in German, if it’s okay. I don’t know if it helps. Maybe!?

@RudolfT, yes please, German is fine. Anything Claude was doing around the time of a crash helps, especially big reads like long lists, Insights or HomeyScripts that return a lot. If it crashes again on 6.2.1, a new diagnostic report will show the memory figures as well, and together that should point to the cause.

6.2.3 is live

6.2.3 keeps each dashboard on its own instead of all of them in one setting. With several big dashboard pages, every edit or page load moved all of them through the app at once, and Homey could stop the app for using too much memory. Existing dashboards are moved over by themselves, so there is nothing to do.

Thanks to @RudolfT for the reports and for digging into what his assistant was doing. That is what found it.

6.2.4 is live

If you use the Homey app on Android: the delete buttons on the settings page work again. They asked a question first that Android never showed, so a tap on Delete did nothing. The question now appears on the page itself.

Also new: an API key needs a name before it is created, and calendar events say whether they repeat, so your assistant can tell a birthday from an appointment.

Thanks again to @RudolfT, who found all three.

@Danny Feature request: expose the device’s Homey-app device type in MCP responses

Danny, thanks for the great MCP AI Bridge! I have a feature request.

In the Homey app you can set a device type / appliance category per device
(the “Aangesloten” field on the device settings screen, e.g. “Lamp” or
“Vaatwasser”). This field is what Homey’s built-in category automations filter
on, such as “all lights off on the ground floor”. In my case a smart plug
powering a dishwasher was accidentally set to type “Lamp”, and a “turn off all
lamps” action switched the dishwasher off mid-program.

The MCP tools (devices_get, devices_get_state, devices_resolve) do not return
this field: they only expose the technical class (e.g. “socket”) and the icon.
As a result, an AI assistant cannot verify whether a device’s type matches the
appliance it actually powers when building or reviewing category-based flows
like "turn off all ".

Request: add the app-configured device type to the device objects in the MCP
responses (e.g. as a “deviceType” field), so an assistant can verify the type
and warn when a plug has the wrong type assigned.

Happy to provide more details or screenshots if useful.
Jeroen

Thanks, Jeroen, good catch, and a nasty way to find out. Homey keeps that setting as the device’s virtual class: the class says what the device is (a socket), the virtual class says what is plugged into it (a lamp, for instance). The bridge already uses it behind the scenes, for example to count the lamps that are on, but the device tools don’t return it yet.

I’ll add it as virtualClass to devices_get, devices_get_state, devices_resolve, devices_list and devices_find in the next version, so your assistant can spot a plug whose type doesn’t match what it powers.

6.3.2 is live

This one is mostly dashboards, built from two long lists by @RudolfT, who rebuilt his whole wall tablet page with the bridge’s own cards:

  • Thermostats for floor heating and radiators, with a round dial, the room temperature, the humidity and whether it heats.
  • Rooms with their sockets and what they use, tags and buttons in the heading, a counter, and any other card in their panel.
  • Chips under the header that only show when they mean something: the washer that is done, the robot vacuum that is cleaning, a room that heats.
  • Rows side by side with icons, units and bars, tiles in a colour of their own or by their value, and more say over columns.
  • A robot vacuum card, one line for all smoke or water detectors, and pictures that open large on a tap.

And for @Jeroen_Marijke_Looye: the device tools now say what is plugged into a socket (virtualClass), so your assistant can spot the dishwasher plug that says it is a lamp.

Every version is in post 3, and your assistant finds every dashboard option in the homey-dashboards skill.

Thanks, Danny!

Confirming it works: after updating to 6.3.2 the device tools now return
virtualClass for my sockets, and my dishwasher plug correctly reports
“dishwasher” instead of being invisible as a “lamp”. Verified both plugs right
after the update.

Great to see a feature request picked up so quickly. This closes a real gap:
my assistant can now verify a plug’s device type when building or reviewing
category-based flows (like “turn off all lights on the ground floor”), so a
mis-typed plug can’t silently switch off an appliance mid-program anymore.

Thanks also for the new dashboard options in this release, looks like a great
update all round.
Jeroen