Currently, enabling MCPs in ClickUp seems to be mainly oriented at the workspace or personal level, which greatly limits their use in organizations where different teams, clients or areas need access to different contexts and tools. It would be very useful to incorporate a granular administration layer that allows you to define where each MCP is available, who can use it and with what permissions. The proposal would be for ClickUp to allow configuring MCPs not only at the global level, but also at the Space, Folder, Subfolder and List levels. In this way, the same workspace could have specific MCPs for different clients, departments or projects, preventing the entire organization from accessing the same context or tools. For example, an MCP connected to a specific customer's information might be available only within that customer's folder or list. In addition, it would be interesting to add individual permissions on the same MCP. That is, not only deciding if an MCP is enabled or not, but also defining which users or roles can use it, manage it, connect it, modify its configuration or simply consult it. This would make it possible to clearly separate usage permissions and administration permissions. At the functional level, the feature could include: Activate or deactivate MCPs by Workspace, Space, Folder, Subfolder or List. Assign specific MCPs to specific areas of work. Define permissions per user, team or role on each MCP. Differentiate between usage, configuration, administration and viewing permissions. Allow inheritance of permissions from higher levels, with the option of overwriting them at lower levels. View from each space/folder/list which MCPs are available and by what permission rule. Create reusable MCPs, but configurable according to the context where they are applied.
