Set up Glean MCP server
The Glean MCP server is fully managed and built into your Glean instance. Glean enables the Glean MCP server for customers by default with OAuth, so users can access Glean in supported AI tools without an admin enabling the server manually.
What's enabled by default
Along with the MCP server, Glean turns on the supporting pieces needed to connect MCP hosts:
- Glean OAuth authorization server — provides OAuth-based authentication for MCP, so supported AI tools can connect without manual OAuth setup.
- Approved-application greenlisting — Dynamic Client Registration (DCR) is restricted to a Glean-managed list of vetted client applications, so only approved MCP hosts can register. See Dynamic Client Registration and the MCP security overview for details.
This default-on configuration applies to customers who haven't already enabled MCP, and to all new customers. Customers who had previously configured MCP or their own OAuth keep their existing settings.
Verify and manage OAuth
The Glean OAuth authorization server is enabled by default. To review or change it, go to Admin Console → Users & permissions → Third-party access (OAuth).
How OAuth fits
The Glean OAuth authorization server provides OAuth‑based authentication for MCP:
- Dynamic clients (DCR) – MCP hosts (such as Cursor, Claude, VS Code) discover Glean at runtime and register themselves using OAuth Dynamic Client Registration.
- Static OAuth clients – Admin‑managed OAuth applications with stable client IDs and redirect URIs, used for specific integrations or external MCP servers that require a fixed client configuration.
You can view and manage these OAuth clients in Admin Console → Users & permissions → Third‑party access (OAuth).
For details, see Glean OAuth Authorization Server.
Share the end-user guide
Provide users the end-user guide for connecting from their host application: Using the Glean MCP Server.
Next steps
From here, you can: