# MCP access for trusted Member accounts

**URL:** <https://community.fibery.io/t/mcp-access-for-trusted-member-accounts/10845>\
**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:** 6

<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:** [May 14, 2026, 7:54am UTC](https://community.fibery.io/t/mcp-access-for-trusted-member-accounts/10845/6 "2026-05-14T07:54:38Z")

</div>

> [@Granular AI Access Control (Space-level AI Permissions)](https://community.fibery.io/t/granular-ai-access-control-space-level-ai-permissions/10580/5):
>
> I think we should consider introducing the concept of AI agents as additional users in the workspace, potentially each under control of a human user. In other words, admins/architects can define what access each (human) user is allowed, and then any user can create ‘delegate AI’ users. By default, the AI users get the the same permissions as their human master, but the user also has the option of restricting them, e.g. making one of their AI delegates a read-only agent, making another limited …

---

_[View the full topic](https://community.fibery.io/t/mcp-access-for-trusted-member-accounts/10845)._