# Glean plugin for coding hosts

The Glean plugin gives Cursor, Claude Code, and Codex users access to Glean Skills and tools. It discovers eligible skills and tools dynamically and runs them through Glean's governed gateway. Installation differs by host, so use the host-specific deployment guide for the current setup path.

## Choose a task[​](#choose-a-task "Direct link to Choose a task")

### [Deploy in Cursor](/administration/platform/mcp/glean-plugin-cursor.md)

[Prepare Glean access and validate the per-user Cursor installation before rollout.](/administration/platform/mcp/glean-plugin-cursor.md)

### [Deploy in Claude Code](/administration/platform/mcp/glean-plugin-claude-code.md)

[Add the marketplace and plugin to a repository.](/administration/platform/mcp/glean-plugin-claude-code.md)

### [Deploy in Codex](/administration/platform/mcp/glean-plugin-codex.md)

[Prepare Glean and validate the per-user Codex installation before rollout.](/administration/platform/mcp/glean-plugin-codex.md)

### [Manage access and security](/administration/platform/mcp/manage-glean-plugin.md)

[Control tool and Skills access, approvals, and monitoring.](/administration/platform/mcp/manage-glean-plugin.md)

### [Troubleshoot deployment](/administration/platform/mcp/troubleshoot-glean-plugin.md)

[Resolve marketplace, authentication, permission, and tool availability issues.](/administration/platform/mcp/troubleshoot-glean-plugin.md)

### [Use the Glean plugin](/user-guide/mcp/glean-plugin.md)

[Share installation, authentication, and usage guidance with users.](/user-guide/mcp/glean-plugin.md)

## Supported hosts[​](#supported-hosts "Direct link to Supported hosts")

* Cursor 3.8.11 or later
* Claude Code
* Codex

Claude Cowork and GitHub Copilot aren't supported.

## Decide whether the plugin fits[​](#decide-whether-the-plugin-fits "Direct link to Decide whether the plugin fits")

The plugin gives users access to Glean tools across the 300+ applications Glean supports, along with your organization's Skills, through a single installation. The alternative is curating a standard Glean MCP server for each team or use case.

Routing requests through Glean keeps:

* Access permission-aware, so users can only search, read, and act on content they can already access in Glean
* Administration centralized in Glean instead of separate configurations for each host or team
* Write-action confirmation requirements in effect regardless of the host

The plugin is a good fit when your users work in a supported host and need access to many Glean tools and Skills. It isn't optimized for a small, controlled subset of connector tools. For that use case, configure a [standard Glean MCP server](/administration/platform/mcp/create-mcp-servers.md) and choose the exact tools to expose.

Using the plugin doesn't affect your Glean usage consumption.

## Prerequisites[​](#prerequisites "Direct link to Prerequisites")

Before you deploy the plugin, complete the following prerequisites:

* Enable the [Glean OAuth authorization server](/administration/oauth/authorization-server.md)
* Configure [Dynamic Client Registration](/administration/oauth/dynamic-client-registration.md) according to your organization's OAuth policy
* Enable the tools and Skills your users need and make them visible to the intended users or groups

### Configure Dynamic Client Registration[​](#configure-dynamic-client-registration "Direct link to Configure Dynamic Client Registration")

The plugin authenticates through Glean's OAuth authorization server and registers itself using Dynamic Client Registration (DCR).

1. In the **Admin console**, go to **Third-party access**.

2. Open **Manage settings** for **Dynamic client registrations (DCR)**.

3. Choose an option:

   <!-- -->

   * **Allow any application** lets users register any application that supports DCR
   * **Allow approved applications** restricts registration to an approved list. Include **Glean CLI** so the plugin can register

4. Click **Save**.

![Dynamic client registration settings in the Glean Admin console, with Allow any application selected.](/img/administration/mcp/glean-plugin/dcr-allow-any-application.png)

Dynamic client registration settings with Allow any application selected

If you choose **Allow approved applications**, select the lists that registration is restricted to.

![Allow approved applications expanded, with the Glean-managed and custom application lists selected.](/img/administration/mcp/glean-plugin/dcr-approved-applications.png)

Approved application lists for dynamic client registration

For more information about each option, see [Dynamic Client Registration](/administration/oauth/dynamic-client-registration.md).

## See also[​](#see-also "Direct link to See also")

* [About Glean MCP server](/administration/platform/mcp/about.md)
* [Glean MCP Gateway](/administration/platform/mcp/mcp-gateway.md)
* [Deploy an MCP server with MDM](/administration/platform/mcp/mdm-mcp.md)
* [Human-in-the-loop confirmations for write tools](/tools/human-in-the-loop-experience-for-tools.md)