Glean - Resolve AI

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 create a Client API token, and the MCP endpoint URL for your Glean tenant (typically https://<tenant>-be.glean.com/mcp/default).

1. Create a Glean Client API token

Follow Glean’s API token setup guide.
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

Set up the integration either in the Resolve UI or in the Satellite configuration.

Resolve UI
Satellite

Connect Via Resolve UI

Log in to Resolve AI.
Open Integrations for your organization.
Click the MCP Integration 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.

Connect Via Satellite

If you route MCP traffic through the 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 MCP Integrations page and should be marked as healthy. See the MCP reference page for additional satellite configuration options (externally-managed secrets, custom auth headers, OIDC).

3. 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 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.”

​1. Create a Glean Client API token

​2. Add the Glean integration in Resolve AI

​Connect Via Resolve UI

​Connect Via Satellite

​3. Test the Glean integration

1. Create a Glean Client API token

2. Add the Glean integration in Resolve AI

Connect Via Resolve UI

Connect Via Satellite

3. Test the Glean integration