Hi Fibery team :slightly_smiling_face: We ran into an AI governance/security issue while trying to use MCP together with sensitive databases. Scenario: We have a separate Finance Space and databases inside containing sensetive financial information. Problem 1 If AI is enabled on the Workspace l…

[image] ID.000: Member accounts cannot connect MCP This should not be the case. It ought to be possible for an MCP client to connect to Fibery using whatever user credentials are used for authentication.

Another practical example: In a company, there may be different levels of automation specialists — for example junior, middle, and senior automation builders. They may need MCP access to build and maintain automations across operational databases. However, they should not have access to sensitive…

Thanks, Chris! :shaking_face: I may have missed something with a Member account then. I’ll check this again on our side.If it works with regular Member credentials and respects that user’s permissions, then it should fully solve our use case. Thank you!

Good call I’ve been getting more worried about this over the last few weeks as the Dunning Kruger effect wears off just a little bit. After the McKinsey/Lilli and Vercel/Roblox incidents I read a little more and reviewed a custom integration. I guess I already knew some of this and did some good h…

[image] Granular AI Access Control (Space-level AI Permissions) Ideas & Features 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/archit…

Our current workaround is to separate accounts by purpose. The idea is: keep a dedicated Admin account only for workspace administration, user management, sensitive databases, etc. do not generate API keys from this Admin account create separate Member accounts for integrations / automatio…

Thanks that makes sense [image] ID.000: create separate Member accounts for integrations / automation / MCP Then you effectively pay a monthly licence for each API key?

Yes :melting_face: It does mean additional paid accounts/subscriptions, but we currently see it as the price for better isolation and peace of mind regarding sensitive data and integrations. And if the number of these accounts stays relatively small, the overhead is still manageable — for example: …

[image] nathan_jay: Then you effectively pay a monthly licence for each API key? Given that an AI agent (or even many of them) can operate more intensely than a human user, do you think it’s fair to pay for them?

@Chr1sG We tried implementing the approach I described above, but ran into another limitation :melting_face: . It seems that only Admin accounts can create and save Automation Rules in databases, while Member accounts — even with Architect permissions on the Space — cannot. Maybe we missed some s…

MCP access for trusted Member accounts

Ideas & Features

Chr1sG May 14, 2026, 7:54am 6

Topic		Replies	Views
MCP and AI agents Ideas & Features mcp	10	231	May 26, 2026
🔮 Fibery's take on AI (vision) News & Announcements	43	1103	April 29, 2026
Private database - my space Ideas & Features	33	1032	April 13, 2026
[DONE] Fibery MCP server Ideas & Features	18	948	August 7, 2025
Additional restrictions specifically to MCP Get Help permissions	2	31	August 6, 2026

MCP access for trusted Member accounts

Related topics