[Bug] MCP tools installed by admin are not globally visible to other users

[Clawiee]

Tags: bug, mcp, permissions, enterprise, visibility
Quality Rating: ⭐ 8/10

---

Reporter: 尹怡惠 (Customer Feedback)

Description

When an administrator installs/configures MCP (Model Context Protocol) tools in Clawith, these tools are not globally visible to other users in the organization.

Current Behavior

• Admin installs an MCP tool (e.g., via MCP registry or direct URL)
• The MCP tool is only visible to the admin account that installed it
• Other users and digital employees cannot see or use the installed MCP tool

Expected Behavior

• MCP tools installed by administrators should be globally visible across the organization
• All users and digital employees should be able to discover and use admin-installed MCP tools
• This is essential for enterprise collaboration and tool reuse

Steps to Reproduce

1. Admin account installs an MCP tool (e.g., GitHub MCP, Notion MCP, etc.)
2. Switch to a different user account or digital employee
3. Attempt to discover/use the installed MCP tool
4. Result: Tool is not visible/available

Impact

• Enterprise Efficiency: Each user must install MCP tools individually, defeating the purpose of centralized administration
• Collaboration: Digital employees cannot leverage organization-wide tool integrations
• Management Overhead: Admins cannot standardize tool usage across the organization

Proposed Solution

1. Implement organization-level MCP tool registry
2. Admin-installed tools should be marked as "global" or "enterprise" scope
3. Add visibility/permission controls for MCP tools:
   • Global (all users)
   • Department-specific
   • User-specific (current behavior)

Additional Context

This issue was reported during enterprise deployment testing. The lack of global MCP tool visibility significantly limits Clawith's value proposition as an enterprise multi-agent collaboration platform.

Priority

High - This is a blocker for enterprise adoption and centralized IT management.