Glean

configure the glean integration to give resolve ai access to your glean indexed knowledge and tools, for use as evidence during investigations glean connects to resolve ai via its mcp server, authenticated with a user scoped client api token capabilities search enterprise content indexed by glean (confluence, google drive, slack, notion, and any other sources glean crawls) look up people, teams, and other entities via glean prerequisites a glean user with permission to mint a client api token, and the mcp endpoint url for your glean tenant (typically https //\<tenant> be glean com/mcp/default ) 1\ mint a glean client api token follow glean's https //docs glean com/administration/platform/mcp/about#glean api tokens create a user scoped client api token (not a global token) so requests carry the acting user's permissions grant the following scopes on the token mcp , agents , search , chat , answers , documents , tools , entities copy the generated token value glean documents these as a required set for mcp access, so the safest path is to grant all of them if your security policy requires narrower scopes, work with glean to confirm which scopes map to the specific tools you want resolve ai to call 2\ add the glean integration in resolve ai configure glean either through the resolve ai cloud ui or via the https //docs resolve ai/resolve satellite , depending on how your organization connects mcp servers via the resolve ai ui log in to https //app resolve ai open https //app resolve ai/integrations for your organization click the https //app resolve ai/integrations/mcpintegration/connect tile configure the connection mcp server url https //\<tenant> be glean com/mcp/default auth method token token the client api token from step 1 click save resolve ai will call tools/list on the glean mcp server to discover the available tools; once the integration shows as healthy, glean is ready to use via the resolve satellite if you route mcp traffic through the https //docs resolve ai/resolve satellite , add an mcpintegration entry to your satellite values yaml integrations glean type mcpintegration create true connection mcpserverurl https //\<tenant> be glean com/mcp/default authmethod token secret token "\<client api token from step 1>" run helm upgrade and ensure the satellite pod restarts (the k8s secret is only re mounted on pod restart) once configured, the integration will appear on the https //app resolve ai/integrations/mcpintegration/edit and should be marked as healthy see the docid\ n2bvcio8e9fsfs7kx5wzb for additional satellite configuration options (externally managed secrets, custom auth headers, oidc) test the glean integration glean's mcp server may advertise its tools under a name like "enterprise document search" rather than "glean " if resolve ai doesn't seem to pick up on "glean" in your queries, you can either reference "enterprise document search" in the query directly, or add a line to your https //docs resolve ai/team knowledge noting that "glean" and "enterprise document search" refer to the same tool chat with resolve ai and ask questions like these to confirm the integration is working "what glean sources do you have access to?" "search glean for the latest runbook on database failover " "use glean to find who owns the payments service "