Skip to main content

Set up the Glean MCP server

Glean's MCP server lets AI agents search and chat across company apps and docs, read documents, and run Glean agents, all permission-aware. This guide covers confirming the Glean MCP server is enabled, creating a static OAuth client, finding your server URL, and adding it to MintMCP.

Prerequisites​

  • A MintMCP admin account
  • A Glean admin account with the Admin role
  • Glean's OAuth authorization server enabled (on by default for most customers; confirmed in the first step below)

Confirm the Glean MCP server is enabled​

  1. Go to your Glean Admin Console and navigate to Users & permissions → Third-party access (OAuth).
  2. Confirm the Glean OAuth Authorization Server shows as enabled.

The MCP server and OAuth authorization server are enabled by default for all Glean customers. If OAuth is not enabled, contact Glean support before continuing.

Create a static OAuth client​

Glean restricts Dynamic Client Registration to a vetted allowlist, so MintMCP must be registered as a static OAuth client.

  1. In the same Third-party access (OAuth) page, find the Static clients section and click Create client.
  2. Fill in the form:
    • Client name: MintMCP (or another descriptive name)
    • Redirect URIs: https://app.mintmcp.com/oauth/callback
    • Scopes: MCP is the default. Glean's authorization server also defines SEARCH, CHAT, AGENTS, DOCUMENTS, TOOLS, and ENTITIES, so add whichever ones match the capabilities you want your team to reach through the gateway.
  3. Click Create.
  4. Copy the Client ID and Client Secret immediately. The secret is shown only once and cannot be retrieved after you close or leave the page.

Get the server URL​

  1. Go to app.glean.com/admin/about-glean.

  2. Find the Server instance field. This shows your backend hostname, for example acme-be.glean.com.

  3. Construct your MCP server URL:

    https://<your-backend-host>/mcp/default

    For example, if your backend host is acme-be.glean.com, your server URL is:

    https://acme-be.glean.com/mcp/default

    The /mcp/default path points to Glean's default MCP server. If your organization has configured a custom MCP server, use /mcp/<server-name> instead.

Add Glean to MintMCP​

Glean is listed as a recommended server in the MintMCP store, so each user authorizes with their own Glean identity through per-user OAuth.

  1. In MintMCP, go to MCP store → Manage store.
  2. Find Glean in the recommended servers and click Install. A configuration screen appears.
  3. In Server URL, enter the URL from the previous step, for example https://acme-be.glean.com/mcp/default.
  4. Set Connection type to Per-user credentials and Authorization method to OAuth.
  5. Open OAuth Client Advanced Settings and paste the Client ID and Client Secret from the static OAuth client you created.
  6. Click Install to finish.

Security considerations​

  • The client secret is shown only once: store it in a password manager or secrets vault immediately after creation.
  • If the client secret is compromised, rotate it from the three-dot menu next to the client in the Glean admin console, then update the value in MintMCP's OAuth Client Advanced Settings.
  • Each user authenticates with their own Glean identity, so MCP tool calls execute with their individual permissions.
  • Glean's permission-aware knowledge graph ensures users can only access documents and data they're already authorized to see in Glean.

Troubleshooting​

  • "Unauthorized" or OAuth callback errors — Glean treats redirect URIs as case-sensitive exact matches. Open the static client in Admin Console → Users & permissions → Third-party access (OAuth) and confirm the redirect URI is exactly https://app.mintmcp.com/oauth/callback.
  • Can't create a static OAuth client — the Glean OAuth authorization server must be enabled before static clients can be created. Navigate to Users & permissions → Third-party access (OAuth) and confirm the server is active. If it isn't, contact Glean support.
  • Server URL returns a connection error — copy the backend hostname directly from the Server instance field on app.glean.com/admin/about-glean rather than constructing it manually. The URL must begin with https:// and end with /mcp/default (or your custom server path).

Next steps​