Remote MCP Server
Connect an MCP host to your organization's Glean knowledge graph and the tools your administrator has enabled. The Remote MCP Server is tenant-specific and permission-aware. Each person uses their own Glean access.
This is different from the public Docs MCP Server, which gives a coding assistant access to Glean developer documentation. Use the Remote MCP Server for your organization's indexed knowledge and configured tools.
Check that you can connect
Glean enables the OAuth Authorization Server and Remote MCP Server by default for eligible tenants. Administrators can disable MCP or hide the end-user Configurator. Open the Configurator first. If it is unavailable, ask an administrator to check your tenant's MCP and OAuth configuration.
Open the MCP Configurator
Open the MCP Configurator and select your host. Copy the current server URL, server name, and host-specific instructions. See the MCP Configurator user guide if the navigation in Glean differs.
If the Configurator or host is missing
Ask an administrator to confirm that MCP servers are enabled, that the end-user Configurator is visible, and to check the DCR allowlist and any prior custom OAuth configuration. Those checks live in Set up Glean MCP server and Dynamic Client Registration.
Match the host to its setup path
Check Supported MCP Hosts to see whether your host is user-configurable or organization-managed. Use that host's URL, server name, and configuration snippet. Do not copy another host's values.
Connect with OAuth
Complete the host's OAuth sign-in flow with your organization's SSO when prompted.
Dynamic Client Registration (DCR) is the usual path for approved MCP hosts. The default policy is the Glean-managed list of approved applications. If DCR is disabled, the host is not approved, or the host needs scopes DCR does not grant, an administrator can register a static OAuth client. See OAuth authentication for the DCR versus static model.
Use a Glean-issued API token only when the host cannot complete OAuth. Do not assign API Token Creator in bulk as an MCP rollout.
Verify the connection
After the host reports that it is connected, start a new conversation and ask something explicit, such as "Search Glean for our engineering onboarding guide." Confirm that the host shows the Glean server and tools, asks for authorization when required, and returns only content you can access in Glean.
If the server is connected but tools do not load, or a verification request fails, follow Remote MCP troubleshooting. Hosts choose which tools to call, so name the data or action you want when you test.
Install individually or manage centrally
Individual installation
Use the MCP Configurator to connect a user-configurable host for yourself.
Organization-managed setup
Configure hosts that your organization manages through administrator controls.
MDM deployment
Deploy a Glean Remote MCP server to managed devices through MDM.
Supported hosts
See configuration ownership, transport, and authentication for each listed host.