From bd655faf6c432e983ae03c50c2bd193ca03534cb Mon Sep 17 00:00:00 2001 From: Eshwar Sundar Date: Wed, 19 Aug 2026 11:44:22 +0530 Subject: [PATCH 1/3] feat(plugins): use harness setup for Claude and Codex --- overrides/claude/root/README.md | 4 ++-- overrides/codex/glean/README.md | 17 +++++------------ .../glean/skills/skill-creation-guide/SKILL.md | 4 ++-- overrides/codex/root/README.md | 15 ++++++--------- .../glean/skills/connect-glean/SKILL.md | 0 shared/glean/README.md | 18 +++++++----------- shared/glean/skills/project-handoff/SKILL.md | 4 ++-- .../glean/skills/skill-creation-guide/SKILL.md | 4 ++-- shared/glean/skills/using-glean/SKILL.md | 3 ++- 9 files changed, 28 insertions(+), 41 deletions(-) rename {shared => overrides/cursor}/glean/skills/connect-glean/SKILL.md (100%) diff --git a/overrides/claude/root/README.md b/overrides/claude/root/README.md index 9e4cba4..2a9ec96 100644 --- a/overrides/claude/root/README.md +++ b/overrides/claude/root/README.md @@ -57,8 +57,8 @@ Restart Claude Code if prompted. `glean` carries everything the old plugins did. /plugin install glean-dev-docs@glean-plugins ``` -Then connect a Glean MCP server — ask Claude to "set up Glean" and the `glean` -plugin's `connect-glean` skill walks you through it. Skills auto-trigger by task. +Then set up Glean by prompting the harness, for example: `Set up Glean for me`. +Complete the browser OAuth flow when prompted. Skills auto-trigger by task. ## Plugins diff --git a/overrides/codex/glean/README.md b/overrides/codex/glean/README.md index 76a8b67..6da66b3 100644 --- a/overrides/codex/glean/README.md +++ b/overrides/codex/glean/README.md @@ -12,18 +12,11 @@ codex plugin marketplace add gleanwork/codex-plugins codex plugin add glean@glean-codex-plugins ``` -### 2. Configure your Glean MCP server +### 2. Set up Glean -Get your server URL and server name from the -[Glean MCP configurator](https://app.glean.com/settings/install?mcpConfigure=true), then run: - -```bash -codex mcp add glean --url https://YOUR-INSTANCE-be.glean.com/mcp/YOUR-SERVER-NAME -codex mcp login glean -``` - -Complete the browser OAuth flow, then verify with `codex mcp list`. Start a new -Codex task so both the bundled skills and Glean MCP tools are available. +Start a new Codex task and prompt the harness: `Set up Glean for me`. Complete +the browser OAuth flow when prompted, then start a new task so both the bundled +skills and Glean MCP tools are available. ## What's Included @@ -42,7 +35,7 @@ per-skill install. They cover: - [Codex](https://developers.openai.com/codex) with plugin support - A Glean account with MCP access -- Your Glean MCP server URL and server name +- A Glean account with MCP access ## Support diff --git a/overrides/codex/glean/skills/skill-creation-guide/SKILL.md b/overrides/codex/glean/skills/skill-creation-guide/SKILL.md index a90a8bb..04e4e1e 100644 --- a/overrides/codex/glean/skills/skill-creation-guide/SKILL.md +++ b/overrides/codex/glean/skills/skill-creation-guide/SKILL.md @@ -39,8 +39,8 @@ time, sub-30-second manual tasks, or things the user will forget exist. When the user asks what they should automate, analyze their work patterns first. -Requires the Glean MCP tools. If they aren't visible, the user hasn't connected -a Glean MCP server — point them at the **connect-glean** skill. +Requires the Glean MCP tools. If they aren't visible, ask the user to set up +Glean by prompting the harness (for example, `Set up Glean for me`). 1. Gather context with Glean: `memory` (roles, responsibilities, active projects), `user_activity` (past ~2 weeks), and `search` for process docs diff --git a/overrides/codex/root/README.md b/overrides/codex/root/README.md index d4d14d4..f8708db 100644 --- a/overrides/codex/root/README.md +++ b/overrides/codex/root/README.md @@ -17,16 +17,13 @@ codex plugin add glean@glean-codex-plugins codex plugin add glean-dev-docs@glean-codex-plugins ``` -Before starting Codex, connect the MCP server used by the plugin you installed: +Before starting Codex, set up Glean by prompting the harness, for example: +`Set up Glean for me`. Complete the browser OAuth flow when prompted, then start +a new Codex task so the bundled skills and MCP tools are available. -- **Glean enterprise knowledge:** get your server URL and name from the - [Glean MCP configurator](https://app.glean.com/settings/install?mcpConfigure=true), - then run `codex mcp add glean --url /mcp/` followed by - `codex mcp login glean`. -- **Glean developer docs:** run - `codex mcp add glean-dev-docs --url https://developers.glean.com/mcp`. - -Then start a new Codex task so the bundled skills and MCP tools are available. +The **Glean developer docs** plugin uses a separate public MCP server. Run +`codex mcp add glean-dev-docs --url https://developers.glean.com/mcp` if you +installed that plugin. ## Plugins diff --git a/shared/glean/skills/connect-glean/SKILL.md b/overrides/cursor/glean/skills/connect-glean/SKILL.md similarity index 100% rename from shared/glean/skills/connect-glean/SKILL.md rename to overrides/cursor/glean/skills/connect-glean/SKILL.md diff --git a/shared/glean/README.md b/shared/glean/README.md index 1b348c5..af0060f 100644 --- a/shared/glean/README.md +++ b/shared/glean/README.md @@ -9,15 +9,11 @@ code exploration, and people discovery directly in your development workflow. Install from the Claude Code plugin marketplace. -### 2. Configure your Glean MCP server +### 2. Set up Glean -Add your Glean MCP server (get your server URL from the [Glean MCP configurator](https://app.glean.com/settings/install?mcpConfigure=true)): - -```bash -claude mcp add glean https://YOUR-INSTANCE-be.glean.com/mcp/default --transport http --scope user -``` - -Restart Claude Code after adding — OAuth authentication is handled automatically on first use. +Start Claude Code and prompt the harness to set up Glean, for example: `Set up +Glean for me`. Complete the browser OAuth flow when prompted, then return to +Claude Code. ## What's Included @@ -32,14 +28,14 @@ by task — there's no per-skill install. They cover: - **Personal productivity** — summarize your own activity, prep status updates, and surface what needs your attention. - **Skill authoring** — discover automation opportunities and generate new skills. -Glean tools are used through whatever Glean MCP server is connected in Claude -Code; if none is configured, see the setup above. +The plugin provides a local Glean MCP server. If no Glean tools are visible, +ask the user to set up Glean by prompting the harness (for example, `Set up +Glean for me`). ## Requirements - [Claude Code](https://claude.com/claude-code) (latest version) - A Glean account with MCP access -- Your Glean MCP server URL (get it from the [Glean MCP configurator](https://app.glean.com/settings/install?mcpConfigure=true)) ## Support diff --git a/shared/glean/skills/project-handoff/SKILL.md b/shared/glean/skills/project-handoff/SKILL.md index b437f79..ab07b75 100644 --- a/shared/glean/skills/project-handoff/SKILL.md +++ b/shared/glean/skills/project-handoff/SKILL.md @@ -22,8 +22,8 @@ This skill drives the standard Glean MCP tools. If the host exposes the a suitable research subagent when subagents are available, or gather the same material directly. For the param shape and pitfalls of `search`, `chat`, `meeting_lookup`, and `employee_search`, see the using-glean reference at -`using-glean/reference/`. If no Glean tools are visible, point the user to the -**connect-glean** skill. +`using-glean/reference/`. If no Glean tools are visible, ask the user to set up +Glean by prompting the harness (for example, `Set up Glean for me`). ## Core Principles diff --git a/shared/glean/skills/skill-creation-guide/SKILL.md b/shared/glean/skills/skill-creation-guide/SKILL.md index 0a3491e..e8fad98 100644 --- a/shared/glean/skills/skill-creation-guide/SKILL.md +++ b/shared/glean/skills/skill-creation-guide/SKILL.md @@ -43,8 +43,8 @@ time, sub-30-second manual tasks, or things the user will forget exist. When the user asks what they should automate, analyze their work patterns first. -Requires the Glean MCP tools. If they aren't visible, the user hasn't connected -a Glean MCP server for this host — point them at their host's Glean MCP setup. +Requires the Glean MCP tools. If they aren't visible, ask the user to set up +Glean by prompting the harness (for example, `Set up Glean for me`). 1. Gather context with Glean: `memory` (roles, responsibilities, active projects), `user_activity` (past ~2 weeks), and `search` for process docs diff --git a/shared/glean/skills/using-glean/SKILL.md b/shared/glean/skills/using-glean/SKILL.md index 3b1238d..60d8702 100644 --- a/shared/glean/skills/using-glean/SKILL.md +++ b/shared/glean/skills/using-glean/SKILL.md @@ -13,7 +13,8 @@ The tools listed below come from the user's Glean MCP server connection. Refer t In the raw MCP tool list, Glean tools appear as `mcp__glean_[server-name]__[tool]` where `[server-name]` is the user's configured server identifier (e.g., `default`, `production`, `acme`). The tool suffix after the final `__` is always consistent across deployments. Use whatever Glean server is visible in your tool inventory. -If no Glean tools are visible, the user hasn't configured a Glean MCP server for this host. Point them at the Glean MCP setup for their host. +If no Glean tools are visible, ask the user to set up Glean by prompting the +harness (for example, `Set up Glean for me`). ## Intent → tool decision tree From adca9a214116081d4e4d8f0f7722d839aff2bb70 Mon Sep 17 00:00:00 2001 From: Eshwar Sundar Date: Wed, 19 Aug 2026 15:29:06 +0530 Subject: [PATCH 2/3] feat(plugins): remove connect skill from Cursor --- .../glean/skills/connect-glean/SKILL.md | 111 ------------------ overrides/cursor/root/README.md | 4 +- 2 files changed, 2 insertions(+), 113 deletions(-) delete mode 100644 overrides/cursor/glean/skills/connect-glean/SKILL.md diff --git a/overrides/cursor/glean/skills/connect-glean/SKILL.md b/overrides/cursor/glean/skills/connect-glean/SKILL.md deleted file mode 100644 index e20dfaf..0000000 --- a/overrides/cursor/glean/skills/connect-glean/SKILL.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -name: connect-glean -description: Help the user connect a Glean MCP server so the Glean skills have tools to call — use when setting up Glean for the first time, adding another Glean server, checking whether Glean is connected, or troubleshooting missing Glean tools. Trigger phrases include "set up Glean", "connect Glean", "configure Glean MCP", "add a Glean server", "is Glean connected", "check Glean status", "Glean isn't working", "no Glean tools", "the Glean tools aren't showing up", "I installed the Glean plugin but nothing happens". Don't use it for actual enterprise queries once connected (use the using-glean skill); this skill only sets up and verifies the connection. ---- - -# Connect Glean - -The Glean plugin ships skills but **does not bundle an MCP server** — the skills -call whatever Glean MCP tools the host exposes. If no Glean MCP server is -connected, the skills have nothing to call. This skill connects one, or verifies -and troubleshoots an existing connection. Follow the section for the user's host. - -## When this applies - -- **First-time setup** — the Glean plugin is installed but no Glean tools appear. -- **Adding another server** — e.g. a second backend or a code-search server. -- **Status / troubleshooting** — "is Glean connected?", "no Glean tools showing". - -## What you need first (all hosts) - -Gather these once, then apply them in the host-specific step: - -1. **Server URL** — the Glean backend, found at - . Looks like - `https://acme-be.glean.com` or `https://be-4f5226e2.glean.com`. -2. **Server name** — organization-specific, from the user's Glean admin. Often - `default`. -3. **Friendly name** — what to call it in the host. Use `glean` for a single - server, or `glean-` when adding several (e.g. `glean-default`, - `glean-code`). - -The MCP endpoint is always `/mcp/`. It is a **remote -HTTP** server and uses OAuth — there is no API key to paste. Follow the -host-specific authentication and reload steps below. - -## Claude Code - -Run: - -```bash -claude mcp add /mcp/ --transport http --scope user -``` - -Verify with `claude mcp list` (look for a `glean.com/mcp` URL). Restart Claude -Code; authenticate on first use. - -## Codex - -Run: - -```bash -codex mcp add --url /mcp/ -codex mcp login -``` - -Complete the browser OAuth flow, then verify with `codex mcp list` (look for a -`glean.com/mcp` URL). Start a new Codex task so the MCP tools are available. - -## Cursor - -Add an entry to `~/.cursor/mcp.json`: - -```json -{ - "mcpServers": { - "": { - "url": "/mcp/" - } - } -} -``` - -Restart Cursor; authenticate via OAuth on first use. - -## Other hosts - -Any MCP-capable host can use Glean: register `/mcp/` as -a **remote HTTP** MCP server in that host's MCP configuration, then restart and -authenticate on first use. Consult the host's own MCP setup docs for where its -config lives and the exact field names. - -## Checking status / troubleshooting "no Glean tools" - -If the Glean skills run but report missing tools, the host has no usable Glean -MCP server in the current session or task: - -1. Confirm a server is configured: use `claude mcp list` in Claude Code, - `codex mcp list` in Codex, or inspect the host's MCP config for a - `glean.com/mcp` URL. -2. If none is configured, run the host setup above. -3. If Codex is configured but not authenticated, run - `codex mcp login `, then start a new task. -4. In other hosts, restart the host and trigger OAuth by running any Glean tool - once. - -## Glean developer docs server (separate, optional) - -The `glean-dev-docs` plugin uses a **different, public** server — no URL, server -name, or auth needed: - -- **Claude Code:** - `claude mcp add glean-dev-docs https://developers.glean.com/mcp --transport http --scope user` -- **Codex:** - `codex mcp add glean-dev-docs --url https://developers.glean.com/mcp`, then - start a new task. -- **Other hosts:** register `https://developers.glean.com/mcp` as a remote HTTP - MCP server (no OAuth required). - -## Related skills - -- **using-glean** — once connected, drives enterprise search, Q&A, and synthesis. diff --git a/overrides/cursor/root/README.md b/overrides/cursor/root/README.md index 032855d..efa5112 100644 --- a/overrides/cursor/root/README.md +++ b/overrides/cursor/root/README.md @@ -20,8 +20,8 @@ search, code exploration, and people discovery, right in your editor. Add the **`gleanwork/cursor-plugins`** marketplace in Cursor, then install the **`glean`** plugin (and **`glean-dev-docs`** if you build with Glean). Once -installed, ask Cursor to "set up Glean" and the `glean` plugin's `connect-glean` -skill walks you through connecting a Glean MCP server. +installed, ask Cursor to "set up Glean". If it needs an MCP URL, follow the +Glean MCP configuration steps in the `glean` plugin README. ## Plugins From 821a8943f2f630993e17f7b885177823f72cfb0b Mon Sep 17 00:00:00 2001 From: Eshwar Sundar Date: Wed, 19 Aug 2026 15:34:16 +0530 Subject: [PATCH 3/3] docs(codex): clarify setup and developer docs ordering --- overrides/codex/glean/README.md | 1 - overrides/codex/root/README.md | 13 +++++++------ 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/overrides/codex/glean/README.md b/overrides/codex/glean/README.md index 6da66b3..adead58 100644 --- a/overrides/codex/glean/README.md +++ b/overrides/codex/glean/README.md @@ -35,7 +35,6 @@ per-skill install. They cover: - [Codex](https://developers.openai.com/codex) with plugin support - A Glean account with MCP access -- A Glean account with MCP access ## Support diff --git a/overrides/codex/root/README.md b/overrides/codex/root/README.md index f8708db..0c15419 100644 --- a/overrides/codex/root/README.md +++ b/overrides/codex/root/README.md @@ -17,13 +17,14 @@ codex plugin add glean@glean-codex-plugins codex plugin add glean-dev-docs@glean-codex-plugins ``` -Before starting Codex, set up Glean by prompting the harness, for example: -`Set up Glean for me`. Complete the browser OAuth flow when prompted, then start -a new Codex task so the bundled skills and MCP tools are available. +Start Codex and prompt the harness to set up Glean, for example: `Set up Glean +for me`. Complete the browser OAuth flow when prompted. -The **Glean developer docs** plugin uses a separate public MCP server. Run -`codex mcp add glean-dev-docs --url https://developers.glean.com/mcp` if you -installed that plugin. +The **Glean developer docs** plugin uses a separate public MCP server. If you +installed that plugin, add it before starting a new Codex task: +`codex mcp add glean-dev-docs --url https://developers.glean.com/mcp`. + +Then start a new Codex task so the bundled skills and MCP tools are available. ## Plugins