# MCP access for trusted Member accounts **URL:** \ **Category:** Ideas & Features\ **Created:** [May 13, 2026, 2:14pm UTC](https://community.fibery.io/t/mcp-access-for-trusted-member-accounts/10845 "2026-05-13T14:14:31Z")\ **Posts on this page:** 1\ **Showing post:** 15
**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:** [May 14, 2026, 3:32pm UTC](https://community.fibery.io/t/mcp-access-for-trusted-member-accounts/10845/15 "2026-05-14T15:32:58Z")
Automation scripts can effectively do things that normally require Admin level access, and for that reason we don’t allow them to be created by Members. This is unlikely to change soon (we have it as something to think about, but no concrete plans). > [@ID.000](#): > > At the moment, the built-in automation actions are intentionally very minimal It is certainly not our intention that no-code actions are minimal, quite the reverse. If there are use cases that come up often that can only be achieved with scripting, then we should look at working out how to make them available via no-code actions. Feel free to tell us what’s missing here: > [@ear Feedback needed: scripts in automations that shouldn't be scripts](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560): > > As a part of our focus on simplification, we are looking for use cases that are much more challenging to solve in Fibery than they should be. Automation scripts are a natural suspect here: writing code requires effort, dedicated skills, and Admin rights ([unlike no-code automations](https://community.fibery.io/t/august-14-2024-manage-automation-rules-as-a-creator-new-sidebar-design-expand-cards-to-show-nested-collections/6504/17)). A question to you: what are the scenarios you consider basic and currently have to solve with scripts? Please share your use case alongside your code. If you used to accomplish the same thing but without… > [@ID.000](#): > > it really feels like having a workspace-level toggle to allow Script Actions specifically for Member accounts with Architect permissions would be very valuable. I don’t imagine this will (could) happen, since it would be equivalent to a toggle which allows Architects to have Admin powers 🤷 --- _[View the full topic](https://community.fibery.io/t/mcp-access-for-trusted-member-accounts/10845)._