Turn off MCP on a per-group basis. Added to the access tab of groups. Note: Hudini requires MCP. Turning off MCP for a group will also disable Hudini for the group.
Available now in version 2.49!
Olive Gizmo
•
Sep 16
Agreed. Being able to limit which of our team members can connect to the MCP would be helpful. We don't want our team to use their personal Claude/ChatGPT accounts, so being able to enforce who is allowed to connect would help make that a technical control vs just a policy requirement.
Coffee Moss
•
Aug 25
+1.
Ability to define users, or groups that have access to the MCP in the settings.
If it can get granular enough where certain people could be allowed to use it, but not say use it to edit information, is just read only, and we can control what information they can access via the MCP, that could also be ideal.
Log in to comment and vote
Comments3
Oct 29
PinnedTurn off MCP on a per-group basis. Added to the access tab of groups. Note: Hudini requires MCP. Turning off MCP for a group will also disable Hudini for the group.
Available now in version 2.49!
Olive Gizmo
Sep 16
Agreed. Being able to limit which of our team members can connect to the MCP would be helpful. We don't want our team to use their personal Claude/ChatGPT accounts, so being able to enforce who is allowed to connect would help make that a technical control vs just a policy requirement.
Coffee Moss
Aug 25
+1.
Ability to define users, or groups that have access to the MCP in the settings.
If it can get granular enough where certain people could be allowed to use it, but not say use it to edit information, is just read only, and we can control what information they can access via the MCP, that could also be ideal.