# Custom Apps: Automated QA & debugging

**URL:** <https://community.fibery.io/t/custom-apps-automated-qa-debugging/11338>\
**Category:** Ideas & Features\
**Tags:** ai, mcp, custom-apps\
**Created:** [September 29, 2026, 12:08pm UTC](https://community.fibery.io/t/custom-apps-automated-qa-debugging/11338 "2026-09-29T12:08:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\
**Post date:** [September 29, 2026, 12:08pm UTC](https://community.fibery.io/t/custom-apps-automated-qa-debugging/11338/1 "2026-09-29T12:08:14Z")

</div>

Hey guys! We discussed this long ago with other Fibery partners but i think this subject becomes more relevant than ever when using Claude - Fibery MCP for building Custom Apps.

So once you changed some data field, or relationship or whatever else related to the data structure or data model the app is screwed.

Currently I solve this by running Claude debugging manually. And it’s a pain.

Do you foresee some sort of automation for auditing changes & fixing created bugs due to changes that happened across the Fibery structures/relationships maybe based on the Fibery Log data?

@mdubakov @Chr1sG

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [September 29, 2026, 12:21pm UTC](https://community.fibery.io/t/custom-apps-automated-qa-debugging/11338/2 "2026-09-29T12:21:31Z")

</div>

We have plans for this…

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/7714c0ddc56ac62eed6e0280289d461febeaecd4.png)