Troubleshoot Glean plug-in deployment
Use these checks when users can't load, authenticate, or run tools through the Glean plug-in.
- Confirm your organization uses Cursor 3.8.11 or later
- In Cursor Settings → Marketplace, search for Glean and confirm the plug-in is available
- Install the plug-in by clicking Add to Cursor
- Restart Cursor after installing or updating the plug-in
- Confirm the
gleanwork/codex-pluginsmarketplace and theglean@glean-codex-pluginsplug-in are installed - Run
codex mcp listand confirm the Glean MCP server is active - Run
codex mcp login gleanif authentication is required - Start a new Codex task after installing the plug-in or changing the MCP configuration
- Confirm the
gleanwork/claude-pluginsmarketplace and theglean@glean-pluginsplug-in are installed - Confirm
.claude/settings.jsonis valid JSON - Merge the repository-level configuration with existing Claude Code settings instead of replacing them
- Ask users to run
/reload-pluginsand start a new session
- Confirm the OAuth authorization server is active
- Confirm Dynamic Client Registration is set to Allow any application, or that Glean CLI is in your approved applications list
- If setup requests a Glean server address, provide your organization's Glean instance address
- Confirm the user completed any required application authorization
- If sign-in loops, ask the user to run
/glean_run Reset gleanand authenticate again
Set USE_CLAUDE_PROJECT_DIR to 1 in .claude/settings.json, and add the plug-in's working path to .gitignore. See Deploy the Glean plug-in in Claude Code.
When a write tool's arguments are too long to display, the host may truncate the approval prompt. Tell users to expand the prompt or copy the full arguments into a file before approving the action.
- Confirm the tool or Skill is active for the organization
- Confirm it's shared with the intended users or groups
- Confirm the user has access to the required connector content
- Confirm tool visibility settings include the intended users or groups