Feedback and Ideas

Allow administrators to control whether an MCP server is visible to users, independently of the visibility settings for the tools and actions within that server.

Administrators can currently limit access to individual tools and actions within an MCP server, but the MCP server itself remains visible to all users as an option under their personal connectors.

Users may see servers they cannot successfully configure because they do not have an account or the required permissions in the underlying application. This creates confusion and makes the connector experience feel cluttered.

We are currently running proofs of concept with several MCP servers. Even when access to the tools and actions within a server is restricted, users can still see options such as Canva, Figma, or call transcription applications when they browse connectors via 

https://app.glean.com/settings/datasources

“How do I get a call transcription app A?”

In most cases, users cannot complete setup because they do not have an account in the underlying application, which creates further support chatter the admins don't need.

Add a server-level visibility control that allows administrators to hide an MCP server from users who are not intended to access or configure it.

Ideally, this control would support the same or a compatible scoping model as the existing tool and action visibility settings, such as:

Hidden by default, with access granted explicitly

Allowance for those permissions to propagate to the actions of the tool (nice to have)

Reduces user confusion about which connectors are available to them

Prevents users from attempting to configure integrations they cannot use

Produces a cleaner, more relevant connector experience

Reduces repetitive questions for administrators and support teams

Gives administrators a complete way to manage MCP server exposure, not only the contents of each server

An administrator can configure visibility for an MCP server independently of its individual tools and actions.

Users who are outside the configured scope do not see the MCP server as an available connector.

Users within the configured scope can see and configure the MCP server according to the existing tool and action permissions.

The behavior is consistent for MCP servers in proof-of-concept and production configurations.

Feature Request: Control MCP Server Visibility at the Server Level

Home

Forum

Events

Content

Courses

Collections

People

Contributors

Albums

Groups

Chat

Channels

Tools

Help

Welcome to the Gleaniverse. Empowering work with AI. Connected by knowledge. Growing together. Search Where would you like to start? Join the discussions.

Glean Community

Gleaniverse Community

Copyright

Terms of Service

Privacy Policy

Code of Conduct

Your Privacy Choices

It looks like there is no account associated with the email you provided. The event is for members only. Please complete the application to join our community first.

Thank you for your interest in joining us

Thanks for your interest in joining the event. However, your account is still pending. Once it's approved, you'll be able to register for the event. Please contact us via community@glean.com if you need support.

Pending Approval

Login to the Glean Community to connect with others, attend community events, and more!

Login or Sign Up for even more

To unlock all parts of the community and get the best experience, complete your profile.

Hey, complete your profile

It looks like there is no account associated with the email you provided. Please complete the application to join our community.

Thank you for your interest in joining Glean Community.

Thanks for your interest in joining Glean Community. We will review your request shortly and email you once it's approved. Meanwhile, please feel free to contact us via community@glean.com for any questions.