Skip to main content

Glean Plugin for Claude Code

What’s included

The Glean plugin turns Claude Code into a front door to your company: Glean’s expert skills — search, code exploration, people, meetings, onboarding, productivity — the custom skills your team authors in Glean, and every tool configured centrally in Glean, each paired with skills tuned to use it well. Those tools are surfaced with Glean’s security and permission guardrails fully enforced, all running through a local Glean MCP server so it works as native skills and tools right in your terminal. See everything included in the plugin →

Installation
1
Add the Glean marketplace and install the plugin

Run these commands inside Claude Code.

Add the Glean marketplace
/plugin marketplace add gleanwork/claude-plugins
Install the plugin
/plugin install glean@glean-plugins
2
/glean_run setup my Glean

Connect the plugin to your Glean instance. You only need to do this once per machine.

  1. In Claude Code, run: /glean_run setup my Glean
  2. Enter your work email when prompted.
  3. Finish sign-in in the browser window that opens (Glean OAuth) and approve access.
  4. Back in Claude Code, confirm it reports connected — you now have every skill and tool provisioned for you in Glean, right in your terminal. Search company knowledge, take action across your connected apps, and move through real work faster without leaving the command line.
Optional: fewer permission prompts

Set USE_CLAUDE_PROJECT_DIR to 1 for fewer approval prompts when the plugin reads its skill files.

It’s an environment variable, so add it under the env key of a Claude Code settings.json file:

.claude/settings.json
{
// ...your other Claude Code settings
"env": {
  // ...your other environment variables
  "USE_CLAUDE_PROJECT_DIR": "1"
}
}

Pick the scope that fits:

  • One project — add it to .claude/settings.json (checked into git, shared with your team) or .claude/settings.local.json (just you).
  • Every project — ask your Claude Code admin to set it in your organization’s managed settings (managed-settings.json), which applies to all projects and can’t be overridden locally.

With this on, the plugin writes its skills cache to .claude/tmp/ in your repo, so add that path to your .gitignore:

.gitignore
.claude/tmp/